PowerShell / PowerShell/vscode-powershell
Have a tree sitter grammar to unlock better Powershell experience in VS Code web
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
Hi, VS Code PM here 👋
After discussing with @TylerLeonhardt what would be the best PowerShell experience for vscode.dev and github.dev we think that the best option would be if PowerShell would contribute a Tree Sitter grammar.
With that basic AnyCode language support would work and the experience would be much better.
I understand that adding a Tree Sitter grammar is work, but wanted to open this issue so we start a discussion and in the case that you do not have cycles to do it maybe someone from the community would help.
Thank you very much and let me know what you think
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
No file, test, or implementation entry point is named. Start by reading the VS Code AnyCode requirements and the existing PowerShell extension structure, then define the grammar scope and integration approach; done means a contributed Tree Sitter grammar enables the proposed basic PowerShell experience in vscode.dev and github.dev.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100