Add VS Code settings and analyzer settings to SimpleModule that does not required DSC tooling
- Dominant language
- PowerShell
- Stars
- 243
- Forks
- 46
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 1
Description
> I wonder if it's a good decision to remove the PSSA rules and vscode integration.
> It's ok to not enforce them, but I'd prefer that we still "highlight" non-HQRM practices.
They have not been part of the SimpleModule before (because the wrong template name was used in Plaster manifest). Was about to add them but skipped it due to the current implementation is using DSC Community tooling like DscResource.AnalyzerRules. It does not feel right for the SimpleModule template.
_Originally posted by @johlju in https://github.com/gaelcolas/Sampler/issues/325#issuecomment-917649398_
Contributor guide
Research direction
No files or tests are named. Start by locating the SimpleModule template and its Plaster manifest, then review how its current VS Code and PSSA integration uses DscResource.AnalyzerRules. Done means the template provides the requested settings and highlighting without requiring DSC Community tooling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100