Skip to content

Add the Run Configuration view with build parameters - #18

Merged
ChrisonSimtian merged 1 commit into
developfrom
feature/run-config-parameters
Aug 16, 2026
Merged

Add the Run Configuration view with build parameters#18
ChrisonSimtian merged 1 commit into
developfrom
feature/run-config-parameters

Conversation

@ChrisonSimtian

Copy link
Copy Markdown
Contributor

4/6 of the #2 split. Closes #12. Based on #17.

A webview-view form in the Fallout container for the parameters a local run should pass, stored and rendered as --name value CLI arguments.

Storage choice

Parameters live in workspaceState, not settings. A run configuration describes this checkout — which configuration, which target framework — so it should not follow the user across workspaces, nor land in a committed settings.json where it silently becomes everyone's default.

Quoting

Values are held as a name/value list and only rendered into an argument string at run time, so quoting happens once, centrally: a value containing spaces is quoted and embedded quotes escaped. The alternative — storing a pre-rendered string — pushes that judgement onto every caller.

Nothing consumes the arguments yet; wiring them into the run flow is #14, kept separate so this PR is reviewable as "does the storage and form behave".

🤖 Generated with Claude Code

@ChrisonSimtian
ChrisonSimtian requested a review from a team as a code owner August 14, 2026 23:41
@ChrisonSimtian ChrisonSimtian added the enhancement New feature or request label Aug 14, 2026
@ChrisonSimtian
ChrisonSimtian force-pushed the feature/deployment-view branch from 92d6c2d to 464e75e Compare August 14, 2026 23:49
@ChrisonSimtian
ChrisonSimtian force-pushed the feature/run-config-parameters branch from 4a991d8 to 92dc0dc Compare August 14, 2026 23:50
@ChrisonSimtian
ChrisonSimtian changed the base branch from feature/deployment-view to develop August 16, 2026 12:00
A webview-view form in the Fallout container for the parameters a local run
should pass, stored as `--name value` CLI arguments.

Parameters live in workspaceState rather than settings: a run configuration
describes *this* checkout (which configuration, which target framework), so it
should not follow the user across workspaces or land in a committed
settings.json where it would become everyone's default.

Values are held as a name/value list and only rendered into an argument string
at run time, so quoting is applied once, centrally — a value containing spaces
is quoted and embedded quotes escaped, rather than each caller guessing.

Nothing consumes the arguments yet; wiring them into the run flow is #14.

Closes #12

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ChrisonSimtian
ChrisonSimtian force-pushed the feature/run-config-parameters branch from 92dc0dc to c63654f Compare August 16, 2026 12:11
@ChrisonSimtian
ChrisonSimtian merged commit ffd3c5a into develop Aug 16, 2026
1 check passed
@ChrisonSimtian
ChrisonSimtian deleted the feature/run-config-parameters branch August 16, 2026 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Run Configuration view: build parameters as CLI arguments

1 participant