-
Notifications
You must be signed in to change notification settings - Fork 36
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 syntax error when using AWS intrinsic functions #12
Comments
Thanks for reporting this. You are right syntax is valid per YAML specs - seems to be a bug within Red Hat YAML server, issue open here redhat-developer/yaml-language-server#77) |
Heya from one of the maintainers of cfn-python-lint! We stumbled upon your extension because one of our users was trying to use our extensions together and got hit by the issue described here. Does it makes sense for you to integrate with us for validation instead of a basic YAML linter? I would love to see a consistent tool chain for linting and code completion! |
Hi and thank you for reaching out! I haven't been active in the project for a while so completely missed out your comment. I've checked the rules in cfn-lint and I really like the idea. I would need to spent time with it, as I'm not getting consistent results - both CLI and VS Code extension. I think that cfn-lint can be complementary to YAML language server, which I see as necessary - as it provides additional capabilities (for example format document functionality) |
try updating the list on the readme to what's here: redhat-developer/yaml-language-server#77 (comment) |
Hi there,
Many thanks for adding YAML support to your extension.
I'm hitting the following issue in VS Code when using intrinsic functions:
I assume that this issue is being reported by the "YAML Support by Red Hat" plugin that your plugin now depends on?
I'm not sure how this issue should be resolved i.e. within your plugin, within the configuration of the Red Hat plugin or by changing the syntax of my YAML but obviously I'm conforming to the syntax used by AWS in their examples
Any assistance would be greatly appreciated!
Many thanks
The text was updated successfully, but these errors were encountered: