-
Notifications
You must be signed in to change notification settings - Fork 131
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
Click-to-documentation on terraform registry #409
Comments
@cgriggs01 @aeschright this might be interesting bump for Terraform adoption - i see a lot of people sharing screen with VSCode and this extension installed. This might simplify the user journey. |
this extension does exactly that, maybe the code could be included; https://marketplace.visualstudio.com/items?itemName=Makeshift27015.terraform-documentation-links |
well, i'm requesting it to be baked into official extension, because using code from unverified developers has its own risks 🤷♂️ |
Hi folks! I'm glad to see your support for this feature. We're implementing it on the language server side so I'm going to transfer the issue over there, but you'll see the first part of it in this week's |
Hi folks, We don't have predictable deeplinks for resource or data source docs pages yet, but this feature is tracked under #190 With that in mind I'm going to close this issue. The new release of LS should be automatically available on the next launch of your VS Code, assuming you use our official Terraform extension. |
@radeksimko - but can we have this on the editor level?.. as "lens"? |
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. |
I'm working with tf files a lot and i'd like to click-to-open-in-browser on resource names and resource properties. Terraform registry is having all standard URL format for resource names and property names (just
#property_name
anchors) and it should probably be not that hard to implement it. Would save tons of people tons of time.The text was updated successfully, but these errors were encountered: