Skip to content

feat: show the parked subgraph in the promotion dialog - #385

Merged
Rassl merged 1 commit into
mainfrom
feature/scratchpad-subgraph-ui
Aug 11, 2026
Merged

feat: show the parked subgraph in the promotion dialog#385
Rassl merged 1 commit into
mainfrom
feature/scratchpad-subgraph-ui

Conversation

@Rassl

@Rassl Rassl commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

The dialog showed aggregate property counts only, so an admin approving a schema type could not see which nodes it would promote, nor the relationships between them.

Add a subgraph panel above the property table listing the nodes by name and the relationships joining them. Edges whose other end is parked under a different type are rendered greyed and labelled "still parked" — those are not promoted by this approval, and the resulting node comes out disconnected from that side until the other type is approved too. That distinction is the reason the panel exists; a plain edge list would imply the whole structure survives.

Also surface edge failures after approval. Previously the row spoke up only when ENTRIES failed to promote, so a perfect node promotion with broken relationships read as clean success. edges.pending is deliberately not treated as a problem — it is the expected steady state for a subgraph approved one type at a time.

The dialog showed aggregate property counts only, so an admin approving a
schema type could not see which nodes it would promote, nor the
relationships between them.

Add a subgraph panel above the property table listing the nodes by name
and the relationships joining them. Edges whose other end is parked under
a different type are rendered greyed and labelled "still parked" — those
are not promoted by this approval, and the resulting node comes out
disconnected from that side until the other type is approved too. That
distinction is the reason the panel exists; a plain edge list would imply
the whole structure survives.

Also surface edge failures after approval. Previously the row spoke up
only when ENTRIES failed to promote, so a perfect node promotion with
broken relationships read as clean success. edges.pending is deliberately
not treated as a problem — it is the expected steady state for a subgraph
approved one type at a time.
@Rassl
Rassl merged commit c58c168 into main Aug 11, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant