-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
yaml.schema incorrectly flags property #28
Comments
Might be fixed on latest coc-yaml, also checkout the verbose output from your language server. |
Updated to latest coc-yaml. Problem still occurs. version: v1.0 With this, coc-yaml will flag |
Should be problem of your language server, checkout https://github.com/neoclide/coc.nvim/wiki/Debug-language-server#using-output-channel |
Here's the output from the yaml LSP output channel:
This is my {
"yaml.trace.server": "verbose"
} |
Confirmed this to be an issue with the following versions coc-yaml 1.3.0 |
This is happening for me as well, file name coc: 0.0.80 |
This seems to be an issue with how https://www.schemastore.org/api/json/catalog.json is parsed. |
Appreciate this issue has been open for a while, found it whilst googling as I have the same problem. I have a GCP I am just adding that the latest release of the language server has nothing about this in their changelog so I suspect it's not been fixed. In any case, I have found a workaround that suits me: I disable the schema store in my global config:
Hope this helps anyone else who might still have the issue. |
Any solution to ignoring the |
The solution for me was to {
"yaml.schemaStore.enable": false,
"yaml.schemas": {}
} |
My "solution" was to add this as a header to all my GitHub Actions workflow files... :/
|
There is |
When the filename was `deploy.yml`, the YAML language server extension would warn `Property [property-name] is not allowed.`. In order to solve this problem, I renamed the file. Issue that might related to this problem: neoclide/coc-yaml#28
My coc-settings.json file has the following setting:
That's not a typo. I do not have any yaml schemas configured in my coc-settings.json file.
The Problem
When I edit a yaml file in
.semaphore/deploy.yml
, coc-yaml flags all the top-level properties as invalid with the following message:Why is coc-yaml pulling a schema from deployphp/deployer? This doesn't happen for all yaml files.
The text was updated successfully, but these errors were encountered: