Repository navigation
Conversation
…ector resolver core (102b-flows row 1a) userData.tags (the field behaviours already read) gets a write path: an Inspector Tags section (chips, add on Enter, union over a multi-select as one undo step), its own 'tags' history kind, and objectParameters parameter 'tags' (validated, cleaned again on apply). selectorCore.js is the pure half of the many-target Object Selector: tag / group / name-pattern resolution, outermost match wins, scene order. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…t membership, Fired Object (102b-flows row 1b) An Object Selector with pick tag / group / name resolves to a set (memoised per tick per question). Every effect pair collection fans out over the set, with ONE resolveInputs per edge and a per-member key on the rising-edge maps (Play Animation, Set Expression, physics actions; sound and particle voices get a member id), so every member acts on the same pulse. Triggers fire for any member (reachesObjectSelector, hover, watched objects). A new Fired Object node says which member fired; the stamp carries an additive optional 'obj' field on nodetrigger only when something listens (older peers ignore it, the validator accepts absent). Physics props, jiggle and patrol read the set too. A selector without pick takes the old code path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…r and agent tools see the set (102b-flows row 1c) The Object Selector card gets a pick menu (One object / By tag / By group / By name), a match field (tag suggestions from the scene, a group list, a name glob) and a live count of what it resolves to. pick / match are declared params (legacy 'object'), so create_flow_nodes and describe_node_types take them. Flow lint flags a set that matches nothing (dashed wire + chip, Disconnect); the debugger shows the resolved set for a selector and 'acts on N objects' for a node wired into one. The agent scene check reaches a set's members (no false source-no-object), warns on an empty set, and update_objects takes tags. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…this one; boot half of the selector split out (102b-flows row 2) Object menu (Physics & effects): with several objects selected, 'Give this flow to the selection' copies the clicked object's flow onto the others as plain copies (fresh node ids; references to the source re-pointed at each receiver; an existing flow replaced in place after one confirm, so a Scene-graph embed of it survives). Receivers get userData.flowFrom (the family root, objectParameters 'flowFrom', additive), and any member's menu offers 'Update all copies from this one'. One undo step (flowreplace kind); no new wire type. flowGive.js is a lazy chunk. Boot: selectorPick.js is the boot half (pick tests, tag cleaning, a sync resolveTargets that loads selectorCore.js on first use and when a graph holds a many-target selector); the Inspector Tags section and the card's set fields are lazy chunks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… handler cleans tags inline (102b-flows) play +2.5 KB gz, editor +4.4 KB gz vs v1.72.0 (boot-size.cjs, both ok). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ct cost bench, row 3 zero-change unit (102b-flows) flows-many-102b: tags replicate + survive a reload; a tag selector fans one click out to every member on both peers and the pulse names the member (obj); Fired Object agrees on both; a plain one-object selector sends no obj and acts as before; Give this flow / Update all copies reach the other peer, two undos and a redo replicate. 38/38 green. selector-cost-bench: 200 boxes, prod build, monotonic synthetic clock. One tag selector spinning all 200 = 0.907 ms/tick, 200 single selectors = 0.964, no flow = 0.082: the set adds 0.82 ms over the floor (gate 1 ms) and is no dearer than today's 200 selectors. flowGive: the whole-document 'nodes' message carries the empty scene arrays the validator wants. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…he flowStore chunk, tag helpers lazy (102b-flows) selectorPick.js was a chunk of its own (its lazy importers selectorCore and the debug flowLint import gave it a reach no other module had), so its name joined every lazy import's preload list: ~20 B in a hundred boot chunks plus the chunk's own 0.5 KB. selectorCore now keeps its own copies of the four tiny helpers (a unit test keeps them equal), flowLint tests the pick inline, and flowStore re-exports resolveTargets so the boot half lands in its chunk. normalizeTag(s)/MAX_TAGS/MAX_TAG_LEN moved to selectorCore (lazy); the card's pick tooltips moved to the lazy set-fields component. Boot vs v1.72.0: play +2.1 KB (2119.3/2120.0), editor +3.8 KB (3324.3/3325.0); chunk count back to the base's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ed machine (102b-flows) Co-Authored-By: Claude Opus 5.5 <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.
Roadmap 102 batch 2, lane 102b-flows (scout row 3: one flow for many objects). No own release: rides the next integrator. One commit set per row, so a row can be dropped.
What people get
update_objectstags: [...].*any run,?one character, no wildcard = "contains" (Star*,*coin*,enemy ?).objectoutput gives the same for a set (else its first member).userData.flowFrom). One undo.label/selected/type); a selector withoutpicktakes the old code path (unit test pins it).Forks and the recommendations taken: Q1-Q7 in the lane's QUESTIONS file (plain copies; set output = last fired else first; group = Objects-panel group; glob syntax; one Fired Object node + additive
obj; cost gate reading; self-reference re-pointing).Proof (battery rule 21 Nov: lane suites, no lane battery)
flows-many-102b(two peers + reload, 360 s; inbattery.json). Lane run on the final code (39bfc12, Deck local slot, load ~25): 38/38 PASS, rc=0, no page errors on either peer. One earlier run went red only at B's reload (the page took > 30 s to boot beside a running battery); the suite now gives that reload 120 s (39bfc12).shots2/).scripts/selector-cost-bench.cjs, prod build on the Deck with a monotonic synthetic clock.userData.tags,userData.flowFromand the selector'spick/matchare kept verbatim and survive a v1.72.0 re-save.pick/flowFrom/tags.objand acts on its one object as before.nodetriggergetsobjonly when a set selector or a Fired Object listens.selectorCore(13),flowGive(3); extendedflowLint,runtimeTools85,nodeRegistry. Full suite green (469 files, 5276 tests).npm run buildgreen.boot-size.cjs --diffvs a v1.72.0 build): play +2.1 KB gz (2119.3 of 2120.0), editor +3.8 KB gz (3324.3 of 3325.0). Chunk count is the same as the base's.selectorCore), the Tags section, the card's set fields,flowGive.For the integrator
objectParametersgainsparameter: 'tags'and'flowFrom'(validated).nodetriggergains optionalobj(a uuid; the validator accepts it absent). Older peers ignore all three.userData.tags,userData.flowFrom, objectselector datapick/match.commandsHandler(objectParameters branches),wireValidate(objectParameters) andInspector(sections). Keep both sides.graphdeletebrings the deleted object graph back on the puller. This affects every graphdelete; worth a ticket.docs-fragment.md). Changelog line: "One flow, many objects: tag objects in the Inspector, point one Object Selector at every object with a tag, in a group or matching a name, and a new Fired Object node says which one was clicked or touched. Give an object's flow to the rest of the selection, and update all the copies from any one of them."🤖 Generated with Claude Code