Is it possible to develop vscode extension based on this
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
No files, tests, or entry points are named. First establish whether node-api-dotnet supports a VS Code extension written in C# and identify the relevant extension entry point or sample location; done means a documented feasibility answer and, if supported, a working sample.
Written by the indexing model from the issue text.
Description
Could we develop vscode extension with C# based on this? Is there a sample?
- Dominant language
- C#
- Stars
- 783
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
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.
More from microsoft/node-api-dotnet
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
microsoft/node-api-dotnet#484 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/node-api-dotnet#481 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/node-api-dotnet#486 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/node-api-dotnet#483 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/node-api-dotnet#479 ·
All issues in microsoft/node-api-dotnet
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·