Add the F5 dev loop, and document running the extension from source - #21
Open
ChrisonSimtian wants to merge 1 commit into
Open
Add the F5 dev loop, and document running the extension from source#21ChrisonSimtian wants to merge 1 commit into
ChrisonSimtian wants to merge 1 commit into
Conversation
The repo had no .vscode/launch.json, so the single most standard thing a contributor tries on a VS Code extension — press F5 — did nothing. Running it meant knowing to pass --extensionDevelopmentPath by hand, which was tacit knowledge held nowhere. Two configurations, both compiling first via a preLaunchTask so the host never loads stale out/*.js: the normal one, and a --disable-extensions variant for when something looks wrong and other extensions need ruling out. Both open this repo as the test workspace, which is deliberate — it builds with Fallout, so a build-graph.json is already present and the views populate immediately instead of showing empty-state. docs/developing.md covers the loop, the terminal equivalent, why a view might be empty (including that Deployment is expected to stay empty until ADR-0009 lands), and packaging a .vsix locally. .vscode/** was already excluded from the package, so none of this ships. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ChrisonSimtian
added
the
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Independent of the #15–#20 feature stack — safe to merge whenever.
The repo had no
.vscode/launch.json, so the single most standard thing anyone tries on a VS Code extension — press F5 — did nothing. Running it meant knowing to pass--extensionDevelopmentPathby hand, which was written down nowhere.What's here
.vscode/launch.json— two configurations, both compiling first via apreLaunchTaskso the Extension Development Host never loads staleout/*.js:--disable-extensions, for ruling out interference from your own installed extensions.Both open this repo as the test workspace. That's deliberate: it builds with Fallout, so a
build-graph.jsonis already present and the views populate immediately rather than showing empty-state.docs/developing.md— the loop, the terminal equivalent, why a view might be empty, and packaging a.vsixlocally. Includes the two things that otherwise read as bugs: the Deployment view is expected to stay empty until ADR-0009 lands, andpackage.json's version is0.0.0on purpose..vscode/**was already in.vscodeignore, so none of this ships in the package.🤖 Generated with Claude Code