apollographql / apollographql/apollo-tooling

Document how to test/develop the VSCode extension

Open
#1,499 0 comments 2 reactions 0 assignees View on GitHub
:spiral_notepad: component - vscode
Dominant language
TypeScript
Stars
3k
Forks
460
PR merge metrics
No merged PRs in 30d

Description

Hi!

When trying to add a feature to the VSCode extension (and language server), I had a hard time figuring out how to set things up and actually test my changes. Would probably be nice to document this somehow. Admittedly I'm not an experienced VSCode user or dev, so things I got stuck on might be obvious to others, but I still think some form of basic guide would be very nice.

Contributor guide

Open the contributing guide

Research direction

No specific files or tests are named; first locate the VSCode extension and language-server entry points and try the current development and testing setup. Document the prerequisites, setup steps, and test workflow so a contributor can develop and verify a change without guesswork.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
developer-experience, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.