terraform_deprecated_index: Emit issues based on expression types #90
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.
Fixes #84
The current deprecated index detection is based on lexical analysis. Since the rule lexes every expression walked by
WalkExpressions
, it has the problem of emitting multiple issues for the same expression when walking on nested expressions.This PR switches deprecated index detection from lexical analysis-based to syntax analysis-based. Instead of lexing the walked expression, depending on the expression type, check if it has deprecated indexes.
hcl-parse tells us that the types of expressions we should be dealing with in this rule are
ScopeTraversalExpr
,RelativeTraversalExpr
, andSplatExpr
.This allows the rule to emit only one issue for nested expressions. Additionally, issues can be reported against a more precise range.