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
Support for custom YAML tags #76
Comments
Facing the same problem for CloudFormation templates which have tags like |
Currently as far as I can tell the underlying parser doesn't support custom tags. I'm not sure if that is something that could be easily added to that parser or if its worth changing parsers. |
Having the same issue |
@JPinkney right, it has only built-in support for |
@sanyer I'm going to look into it and compare a few of the options |
@JPinkney cool, thanks :-) |
I realized that the same problem is with Ansible playbooks. It has custom BTW, there is a plugin for atom https://atom.io/packages/linter-js-yaml where this option is supported. |
Does js-yaml provide an AST? Last time I have checked there was only one YAML parser that provided AST. Without an AST we can not provide code assist. |
Related to redhat-developer/yaml-language-server#59 |
@JPinkney awesome, great that there are suitable alternatives |
Is this still being considered? I work with YAML which includes custom tags as well and my files show tons of errors that aren't real. |
It will be added in the release tomorrow. |
Added in 0.0.12 release. |
Some utilities extend YAML syntax with custom tags. For example JJB introduces "include" tags, http://jenkins-job-builder.readthedocs.io/en/latest/definition.html?highlight=!include-raw#module-jenkins_jobs.local_yaml
YAML linter fails on provided examples.
Eg here
it says
unknown tag <!include:> at: '4,5'
.According to documentation, currently there is no way
But custom tags are language feature, see http://www.yaml.org/spec/1.2/spec.html#id2761292 , Example 2.24. Global Tags. This document causes errors too:
Could you implement this spec or add some workaround?
The text was updated successfully, but these errors were encountered: