Skip to content

Better Type/Resource Kind Awareness #1955

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task
awilkins opened this issue Mar 6, 2025 · 0 comments
Open
1 task

Better Type/Resource Kind Awareness #1955

awilkins opened this issue Mar 6, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@awilkins
Copy link

awilkins commented Mar 6, 2025

Language Server Version

0.36.4

Problem Statement

When I ask for suggestions in a given location
It would be helpful if these were constrained to appropriate possibilities

e.g.

Here we are in an array that only accepts vpc security group IDs

Image

The first suggestion here is a route table, which has no attributes which are appropriate as a value in this array.

There's only one security group in this configuration, and there's an obvious single attribute of this resource that is appropriate. Maximum efficiency would be promoted by listing first, resource attributes that can contain appropriate values for this location.

Image

This obviously requires a greatly expanded set of metadata on not just what basic datatype things have (this is a string / I accept a string) but what "kind" of thing they are (I am a security group ID / I am suppose to receive a security group ID), and it's all quite provider specific. But would represent a significant improvement.

Attempted Solutions

No response

Proposal

No response

Related LSP methods

No response

References

No response

Help Wanted

  • I'm interested in contributing a fix myself

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@awilkins awilkins added the enhancement New feature or request label Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant