Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow absolute paths to be specified in yaml.schemas
See original GitHub issueProject relative paths requirement for specifying yaml.schemas is probably a suitable way to deal with VSCode, but definitely not for others.
We suggest to allow using an absolute path for a schema, so, when resolving a schema content, if no project is found or path doesn’t resolve against project, it should be attempted to be resolved as absolute path. This would allow plain yaml edition to work without a project, which is actually not so unusual.
Related issue: https://github.com/eclipse/wildwebdeveloper/issues/461
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@JPinkney Upgrade to YAML LS 0.9.0 is ongoing. I’ll try reproducing it using version 0.9.0 this week.
This bug should be closed because I am using absolute paths for months and they do work quite well. The trick is to use
file://URI which allow only full paths (3 slashes).