puppetlabs / puppetlabs/puppet-editor-services
[Feature Request] Use local puppet-lint (+ plugins) instead of built-in
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 52
- Forks
- 21
- Avg merge
- 15h
- Merged PRs (30d)
- 3
Description
VSCode option to specify which puppet-lint to use
I would like a option, where I could specify to use my own installed puppet-lint (and puppet-lint plugins), instead of the one provided by the extension, OR have a way to enable my puppet-lint plugins with the puppet-lint provided by the extension.
I have a bunch of puppet-lint plugins installed, which all auto-format and lint my code, that makes my life easier. It's annoying to have to type it out in a separate terminal, instead of just using VSCode. That's a whole extra step!
Also, I don't see the "problems" that puppet-lint plugins provide, in the "Problems" pane in VSCode - that would also be amazing, and would speed up coding!
As a user / developer
I would like to automatically format my puppet manifests using my own puppet-lint and puppet-lint plugins
so that I don't have to remember to do it myself.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the VSCode integration and how the extension invokes its provided puppet-lint. Determine how a user-selected executable, puppet-lint plugins, formatting, and Problems-pane diagnostics should be configured; done means the requested local linting and plugin feedback work through VSCode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100