Go-to-definition/go-to-references for each.*/for_each

[radeksimko]

Background

This is a follow-up to #861 where we decided not to treat each.* as actual reference origins and similarly not treat for_each attribute as a target.

This has some implications on the UX and some future work.

Go To Definition

While the benefit isn't as obvious in a simple and short config, there are cases where a module or a resource may not fit on the screen. Secondly, as a user I'd just expect "go-to-definition" to always work for any reference, if that reference points somewhere in the code.

Go To References

Similar as above, there can be a number of each.* references and it would be reasonable to expect "go-to-references" to just work in that context.

Config Resolution

There are features which will rely on our ability to resolve references within the config, for example:

• Consider exposing evaluated config as data to code lenses hcl-lang#132
• Show interpolated expression values on hover #495
• Reflect default values in (module & core) completion and hover #956

Proposal

TODO

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.