updated settings to reduce YAML parse errors/complaints #26
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aws-scripting-guy
approved these changes
May 1, 2019
Owner
aws-scripting-guy
left a comment
aws-scripting-guy
left a comment
There was a problem hiding this comment.
Thank you, looks good to me.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding a couple extra data type specifiers in the
settings.jsonexample will reduce the number of errors by default in CloudFormation YAML. This addresses #12 and is basically the workaround mentioned in the comments in redhat-developer/yaml-language-server#77. I was getting the error mentioned in #12 myself, but with these in my User Settings, I no longer get the error.