PowerShell / PowerShell/PSScriptAnalyzer
Support running in ConstrainedLanguage mode
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Summary of the new feature
As a user, I want to be able to invoke PSScriptAnalyzer while running in ConstrainedLanguage mode.
As a user I want to be able to see Diagnostics in VS Code while I'm using the PowerShell extension for VS Code which supports running in ConstrainedLanguage mode.
Proposed technical implementation details (optional)
I think the module would have to be 100% binary and not rely on AddScript(foo, useLocalScope: false).
What is the latest version of PSScriptAnalyzer at the point of writing
1.19
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 investigating how PSScriptAnalyzer invokes AddScript(foo, useLocalScope: false) and how its module is packaged. The work is done when PSScriptAnalyzer can run in ConstrainedLanguage mode and diagnostics appear through the PowerShell extension for VS Code in that mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- devtools, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100