PowerShell / PowerShell/vscode-powershell
Plan of porting over some features from PowerShell Pro Tools extension
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- I have written a descriptive issue title.
- I have searched all issues to ensure it has not already been reported.
Summary
Now that the PowerShell Pro Tools extension by @adamdriscoll extension has been open-sourced it may make sense to look at migrating many, if not all, of the features across to this extension as to provide the best experience in the future
This issue is to discuss whether this is the direction we want to go and if so what parts could be migrated in to this repo along with in future a potential time-frame for this & follows on from this comment from that @JustinGrote raised in the Pro Tools Repo
Proposed Design
No response
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
Review the PowerShell Pro Tools extension and the linked discussion in its issue 43 to identify which features might be migrated into vscode-powershell. The issue needs an agreed feature scope and timeline before implementation can be considered complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100