PowerShell / PowerShell/vscode-powershell
Enable partial support in untrusted workspaces
Open
Nobody has claimed this yet.
Area-Workspaces
Issue-Enhancement
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Separate from #3334, with some effort we could enable the extension in untrusted workspaces if we carefully restrict certain user settings with restrictedConfigurations and code paths with the isTrusted API. However, this is feature work we do not yet have scheduled.
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 reviewing related issue #3334 and the VS Code extension paths that use restrictedConfigurations and the isTrusted API. Define which settings and code paths must remain restricted, then verify that the extension provides partial support in untrusted workspaces without exposing those capabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100