-
Notifications
You must be signed in to change notification settings - Fork 179
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
meta: Support for external linters #635
Labels
enhancement
New feature or request
linting
Functionality related to linting and external linters
meta
needs-research
Comments
danieldreier
changed the title
Meta issue: tflint and other external tool integrations
Meta issue: tflint support
May 18, 2021
radeksimko
changed the title
Meta issue: tflint support
meta: Support for external linters
May 19, 2021
This was referenced Apr 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
linting
Functionality related to linting and external linters
meta
needs-research
Problem Statement
Many advanced users of Terraform leverage a number of external tools, to help them e.g.
Examples of tools
terraform test
Such users would benefit from a more seamless integration with these tools, such that they don't need to leave the comfort of their IDE to run the tool and receive any relevant diagnostics natively - so they're able to address any problems quickly and easily.
Technical Details
While tools may each serve different purpose, they have something in common:
$PATH
User Impact
Any users which use any of the above tools would benefit from closer integration.
See also
Expected User Experience
Users will be able to run the configured linters:
terraform validate
todayUsers will receive diagnostics in the
Problems
pane after the linter runs, similar to how they receive diagnostics for HCL syntax issues e.g.Proposal
It would make sense for the integration to take the above patterns into account and keep in mind possible further integrations that have such commonalities.
There is some potentially relevant prior art to be seen in the Go VS Code extension:
The text was updated successfully, but these errors were encountered: