feat(studio): edit a whole selection in the inspector, delete it in one undo - #78
Merged
Merged
Conversation
This was referenced Jul 27, 2026
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.
feat(studio): edit a whole selection in the inspector, delete it in one undo
What changed
Multi-selection now does more than copy/duplicate. Select several elements of the
same kind, or several data flows, and the inspector edits all of them.
(mixed)(none)removes it from every selected objectWhy
onSelectionChangekept onlyselectedNodes[0]andselectedEdges[0], soeverything downstream of the selection was single-object by construction
(STU-002). Widening that one piece of state and changing the three property
writers to take
string[]is most of the feature — a single selection is justthe one-element case, so there is still only one code path, not a parallel
"bulk" one.
Design notes
(mixed)is a disabled option, so it can never be committed. Opening theinspector on a mixed selection must not flatten the values it is showing — only
a control the author actually changes is written. A property set on
some-but-not-all of the selection counts as mixed rather than as the value one
object happens to hold.
Mixed kinds refuse typed editing, on evidence rather than caution. The schema
declares
AuthenticationSchemefor bothprocessandexternal, but externalaccepts
TokenandPublicKeyand process does not — one shared control wouldoffer values the schema rejects for part of the selection. (
AlgorithmandMultiplicityare identical across their kinds, so a name-based intersectionlooks safe right up until it isn't.) Elements and flows share nothing at all.
Both cases still offer delete, which is unambiguous.
Names are not offered across a selection. A name identifies one object.