Relative paths for schemas not working anymore
See original GitHub issueHi,
I have a JSON schema file in my project that I want to apply to several YAML files.
This is my .vscode/settings.json
:
{
"yaml.format.enable": true,
"yaml.schemas": {
"./my.schema.json": "*.repo.yml"
}
}
where ./my.schema.json
is the relative path to my JSON schema file.
This configuration was working as intended until yesterday. Now it only works if I specify an absolute path for the JSON schema file.
Any ideas?
Thanks 😄
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
JSON schema $ref does not work for relative path
So the issue is I cannot have a ref pointing to a ref(2 levels). But I can have a ref pointing to a...
Read more >OpenAPI Specification v3.0.3 | Introduction, Definitions, & More
The path is appended (no relative URL resolution) to the expanded URL from the Server Object 's url field in order to construct...
Read more >17.7.0 API Reference - joi.dev
isSchema(schema, [options]). Checks whether or not the provided argument is a joi schema where: schema - the value being checked.
Read more >Why relative URLs should be forbidden for web developers
A relative url is a url that is not complete. Usually it's just the last part (the path) of a url, which means...
Read more ><appSettings> element for <configuration> - .NET Framework
Specifies a relative path to an external file containing custom application ... not the location of the application configuration file.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m unsure what would have broke but I’ll look into it.
Just released. It should be fixed. Apparently the language client dependency switched from relative paths to absolute paths so I just had to lower that and it should be back to normal.