fix: avoid checking the schema in case of syntax errors #396
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.
The invalid config below:
generates an error when calling the hashicorp parse.ParseHCL() function but it populate its
parse.Files()
with an invalid data structure for the file's body... for the case above, it creates an attribute with name "wants" and value of type cty.DynamicValue that's not even nullable (attrVar.IsNull() returnsfalse
)...So we cannot have syntax error + schema errors because they do not provide partial correct nodes.
The fix was making terramate check the schema only for the files successfully parsed (valid HCL).
I got this issue while experimenting with the VSCode extension. The Language Server crashed with log below: