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

schemaStore.enable setting does not work as expected #721

Closed
tornike opened this issue Mar 19, 2022 · 2 comments · Fixed by redhat-developer/yaml-language-server#688
Closed
Assignees
Labels

Comments

@tornike
Copy link

tornike commented Mar 19, 2022

Because schema matching is not perfect I prefer yaml.schemaStore disabled, but every time vscode window is reloaded, even though setting is set to "false", schemas are applied anyway.
I have to enable this setting and then disable it manually and schemas are removed, but I have to do this procedure on every vscode reload/restart.

Expected Behavior

When yaml.schemaStore.enable is set to "false", it should be considered even after reloads.

Current Behavior

After reload/restart yaml.schemaStore.enable has no effect.

Steps to Reproduce

  1. Create file named "deploy.yml" in .github/workflows directory. 2 schemas should be applied Deployer Recipe and GitHub Workflow.
    image
    Deployer Recipe shows some errors.
  2. Go to the settings and set yaml.schemaStore.enable to "false". Errors should disappear.
  3. Close and reopen vscode or just run "Reload Window" from command Palette. Even though schemaStore is disabled now, schemas are applied anyway and Deployer Recipe again shows errors.
  4. Now you can enable schemaStore and disable it again and errors disappear.

Environment

  • VSCode version: 1.65.2
  • Extension version: v1.5.1
  • OS: Ubuntu 20.04.1
@rickygao
Copy link

rickygao commented Mar 20, 2022

I am also suffering this, with the same vscode version and extension version on macOS Monterey.

@gorkem gorkem added the bug label Mar 20, 2022
@gorkem
Copy link
Collaborator

gorkem commented Mar 20, 2022

I can reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants