dsccommunity / dsccommunity/SqlServerDsc
SqlServerDsc: Rule TypeNotFound is excluded, but is still enforced
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 385
- Forks
- 224
- PR merge metrics
- No merged PRs in 30d
Description
In Visual Studio Code when coding classes or commands that reference classes or referencing SMO types the rule TypeNotFound is enforced. The rule is excluded in the file .vscode/analyzersettings.psd1 but it is still enforced. If possible we should not enforce the rule TypeNotFound inside Visual Studio Code.
But, we should still support it in QA tests which uses the same Scrip Analyzer configuration file .vscode/analyzersettings.psd1.
See issue #1771 how the rule should be run on built module only. So this issue and issue #1771 must work in tandem, or we might just have to live with seeing the rule fail in VS Code.
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 with .vscode/analyzersettings.psd1 and compare how Visual Studio Code and QA tests consume its PSScriptAnalyzer configuration. Use issue #1771 as the related requirement; done means TypeNotFound is not enforced in VS Code while remaining supported for QA tests on the built module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, vscode
- Domain
- testing, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100