dsccommunity / dsccommunity/SqlServerDsc
SqlServerDsc: Script Analyzer rule TypeNotFound should only run on built module
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 385
- Forks
- 224
- PR merge metrics
- No merged PRs in 30d
Description
Currently the QA test runs all rules on all source files found in folder source. Some rules should not run on the source files, for example the rule TypeNotFound. The rule TypeNotFound will fail when the module contain classes that reference each other since they are in different source files. In this case the rule can only run on the built module. Currently the rule TypeNotFound is excluded from QA tests.
The QA tests should be extended to also run on the built module and make sure the rule TypeNotFound is run.
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
Locate the QA test that applies Script Analyzer rules to files under source, then trace how the built module is produced. Check how TypeNotFound is currently excluded, extend coverage so it runs against the built module, and run the QA suite to verify the rule passes there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100