Build/Deployment/Run Configuration views + Explorer dock#2
Draft
ChrisonSimtian wants to merge 1 commit into
Draft
Build/Deployment/Run Configuration views + Explorer dock#2ChrisonSimtian wants to merge 1 commit into
ChrisonSimtian wants to merge 1 commit into
Conversation
Restructure the single Targets view into several collapsible Views in the Fallout container, and mirror the build targets into the file Explorer. - Build view: the existing target tree, registered under both fallout.build (Fallout container) and fallout.buildExplorer (Explorer dock) — one provider, two homes; refresh updates both. - Deployment view: placeholder pending a deployment-graph.json from the CD model (ADR-0009); shows welcome content for now. - Run Configuration: a webview-view form for parameters (workspaceState → CLI args) and secrets (SecretStorage → env vars, values never rendered). - Run flow: ▶ applies the saved run config silently; "Run with Parameters…" prompts an InputBox prefilled with target + saved args before running. Relates to #1 (this adds the Run Configuration view; declaration-driven population of params/secrets from the build graph is the remaining part, blocked on Fallout-build/Fallout#499). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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.
Draft. Restructures the extension's single Targets view into several collapsible Views, mirrors the build targets into the file Explorer, and adds a Run Configuration form.
What's in it
fallout.build) and the file Explorer (fallout.buildExplorer); oneTreeDataProvider, two homes.deployment-graph.jsonfor the ADR-0009 CD flow.--name valueargs) and secrets (SecretStorage → env vars; values never rendered).Scope / relation to #1
Relates to #1. This delivers the Run Configuration view (the vessel); #1's real ask — declaration-driven population (e.g.
NuGetApiKeyappearing automatically from the build's[Parameter]/[Secret]members) — is not in this PR and stays open. It's blocked on Fallout-build/Fallout#499 (the graph must emitparameters[]first). So this PR does not close #1.Verify
npm run compileclean; newsrc/runConfig.ts..fallout/temp/build-graph.json.