Align hcl.Block
& hclsyntax.Block
DefRange
#487
Merged
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.
This patch fixes a minor discrepancy between
hclsyntax
andhcl
in how DefRange is computed for a block.DefRange of the "higher-level"
hcl.Block
(typically used by most applications) ends with the last label.DefRange of the "lower-level"
hclsyntax.Block
ended with the opening brace{
(i.e. at least 2 characters further).Here we align the low-level API with the high-level one, meaning that most consumers should not be affected by this change, partly because they use
hcl.Block
(which isn't changing) or because they use DefRange to inform some non-critical decisions such as enriching diagnostics.I ran into this discrepancy when working on adding support to JSON syntax to the language server in hashicorp/hcl-lang#88