Repository navigation
feat(graph): require payload cases in traversal - #5818
Conversation
🦋 Changeset detectedLatest commit: 26f4866 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Address "Keyed cases erase wildcard fallback paths" and tag public traversal types for export stability.
Why
Payload-free defaults can make payload-reading transitions throw or leave states unreached. Graph discovery now requires samples for known event types with required payload fields.
What changed
eventscases and snapshot generators. Maps retain unconfigured payload-free, wildcard, invoke completion, error, and delayed samples.Scope
Blast radius
Callers with known required payload events must now provide cases. Event arrays and callbacks returning arrays keep replacement semantics; keyed maps augment applicable machine events.
Verification
pnpm test --maxWorkers=2 --minWorkers=1 --silent: 4,507 passed, 32 skipped, 3 todo across 270 files.