Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relative paths for schemas not working anymore #92

Closed
labarilem opened this issue Jun 12, 2018 · 10 comments
Closed

Relative paths for schemas not working anymore #92

labarilem opened this issue Jun 12, 2018 · 10 comments
Assignees
Labels

Comments

@labarilem
Copy link

Hi,

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 😄

@JPinkney
Copy link
Contributor

I'm unsure what would have broke but I'll look into it.

@JPinkney JPinkney added the bug label Jun 12, 2018
@JPinkney JPinkney self-assigned this Jun 12, 2018
@matulkum
Copy link

+1

@matulkum
Copy link

maybe it was not a change on the extensions, which broke it, but an update from vscode?

@labarilem
Copy link
Author

Hi @JPinkney , any updates? 😄

@JPinkney
Copy link
Contributor

JPinkney commented Jul 2, 2018

Should be in the next release on July 9th.

@labarilem
Copy link
Author

This issue is still present using the latest VSCode version.

@JPinkney
Copy link
Contributor

That's because it hasn't been released yet. There has been issues with the release process that we are still trying to figure out.

@gdimauro
Copy link

any updates?

@JPinkney
Copy link
Contributor

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.

@labarilem
Copy link
Author

I can confirm that it's working now, thanks 😄

bleach31 pushed a commit to bleach31/vscode-yaml that referenced this issue Jan 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants