Rename the Targets view to Build, under a versioned view id - #15
Open
ChrisonSimtian wants to merge 1 commit into
Open
Rename the Targets view to Build, under a versioned view id#15ChrisonSimtian wants to merge 1 commit into
ChrisonSimtian wants to merge 1 commit into
Conversation
ChrisonSimtian
added
enhancement
This was referenced Aug 14, 2026
ChrisonSimtian
removed
the
breaking-change
Groundwork for the Deployment and Run Configuration views: the container is about to hold several views, so the single "Targets" view becomes "Build" and moves to a namespaced id. `falloutTargets` -> `fallout.build` would be a breaking change against a released extension — it invalidates keybindings with a `view ==` when-clause, saved layout state, and user-written when-contexts. Nothing has been published yet, so there is no such state anywhere, which is exactly why the naming gets settled now rather than after the first release. The view's contents and behaviour are unchanged. Closes #9 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ChrisonSimtian
force-pushed
the
feature/build-view-restructure
branch
from
August 14, 2026 23:49
80e407b to
b9fc023
Compare
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.
First of six, splitting #2 into one PR per feature so each lands as its own release-note line. Closes #9.
Groundwork for the Deployment and Run Configuration views: the container is about to hold several views, so the single "Targets" view becomes "Build" and moves to a namespaced id.
Not a breaking change
falloutTargets→fallout.buildwould break a released extension — it invalidates keybindings with aview ==when-clause, saved layout state, and user-written when-contexts. Nothing has been published to either marketplace yet, so none of that state exists anywhere.That is precisely why the naming gets settled now. #17 declares the Deployment view partly for the same reason: fixing ids before the first release means later work is a provider change, not a user-visible reshuffle.
The view's contents and behaviour are unchanged.
Stack
Each is based on the previous, so its diff shows only its own change. Merge in order.
🤖 Generated with Claude Code