You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users benefit from having less accurate schema if the other option is not having any, but as we expose schemas which may not be accurate - e.g. via #302 - we should also find some ways of communicating this to the user.
Proposal
Obtain provider versions via the existing terraform-exec integration (i.e. terraform version output) and put these next to its namespace in the Detail field of the schema, which would then be reflected in the UI.
Examples from Sublime Text:
Examples from VS Code:
The text was updated successfully, but these errors were encountered:
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 context necessary to investigate further.
ghost
locked as resolved and limited conversation to collaborators
Jan 3, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current Version
Use-cases
Users benefit from having less accurate schema if the other option is not having any, but as we expose schemas which may not be accurate - e.g. via #302 - we should also find some ways of communicating this to the user.
Proposal
Obtain provider versions via the existing terraform-exec integration (i.e.
terraform version
output) and put these next to its namespace in theDetail
field of the schema, which would then be reflected in the UI.Examples from Sublime Text:
Examples from VS Code:
The text was updated successfully, but these errors were encountered: