Skip to content

Add the Deployment view as a declared placeholder - #17

Merged
ChrisonSimtian merged 1 commit into
developfrom
feature/deployment-view
Aug 16, 2026
Merged

Add the Deployment view as a declared placeholder#17
ChrisonSimtian merged 1 commit into
developfrom
feature/deployment-view

Conversation

@ChrisonSimtian

Copy link
Copy Markdown
Contributor

3/6 of the #2 split. Closes #11. Based on #16.

Registers fallout.deployment with a provider that returns nothing, so the view renders welcome content explaining what will appear there.

Why ship it empty

The continuous-delivery model — channels → environments → targets (ADR-0009) — is emitted by the framework, not derived here, so there is nothing to render until a Fallout build writes a deployment-graph.json.

Declaring the view now fixes its id and its position in the container. Filling it in later becomes a provider change rather than another user-visible reshuffle of the kind #15 just made — which is the whole reason to do it in this pass rather than when the graph arrives.

Refresh applies to it too, so it picks up a deployment graph the moment one appears, without a window reload.

🤖 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/build-explorer-dock branch from fd68ec2 to 65888af Compare August 14, 2026 23:49
@ChrisonSimtian
ChrisonSimtian force-pushed the feature/deployment-view branch from 92d6c2d to 464e75e Compare August 14, 2026 23:49
@ChrisonSimtian
ChrisonSimtian changed the base branch from feature/build-explorer-dock to develop August 16, 2026 11:59
Registers `fallout.deployment` with a provider that returns nothing, so the
view renders its welcome content explaining what will appear there.

Deliberately shipped empty rather than held back. The continuous-delivery model
— channels → environments → targets (ADR-0009) — is emitted by the framework,
not derived here, so there is nothing to render until a Fallout build writes a
`deployment-graph.json`. Declaring the view now fixes its id and its place in
the container, so filling it in later is a provider change rather than another
user-visible reshuffle of the kind #9 just made.

Refresh applies to it too, so it picks up a deployment graph the moment one
appears without needing a window reload.

Closes #11

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ChrisonSimtian
ChrisonSimtian force-pushed the feature/deployment-view branch from 464e75e to 946d1a8 Compare August 16, 2026 12:11
@ChrisonSimtian
ChrisonSimtian merged commit 1fd052b into develop Aug 16, 2026
1 check passed
@ChrisonSimtian
ChrisonSimtian deleted the feature/deployment-view branch August 16, 2026 12:11
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.

Deployment view

1 participant