Go to module output declaration from reference

[radeksimko]

Use Cases

Users which call modules and need to utilize module outputs will receive some available details about these outputs as part of completion, such as the name of the output, its type (in case of statically defined outputs), description, and whether it's sensitive.

It may still be useful for some users to review the full declaration of the output block within the called module to understand any side effects or implications.

Expected User Experience

User would use Go to definition or Go to declaration from the context menu:

which would bring up the peek view with two locations - the module call itself, i.e.

and the relevant output block within that module

Proposal

hashicorp/hcl-lang

• [ ] Introduce *PathTarget field to schema.Targetable
• [ ] Update reference target collection logic such that it can also collect the additional PathTarget in https://github.com/hashicorp/hcl-lang/blob/f24c834260e015170a294693b9971e4ff1c219ab/decoder/reference_targets.go#L220-L247

hashicorp/terraform-schema

• [ ] Set the new *PathTarget field of Targetable to relevant values in https://github.com/hashicorp/terraform-schema/blob/d31af62318148744949c88650a363ac1860f1383/schema/module_schema.go#L64-L70

[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.