fix: accept omitted condition in fallback transitions #378
Reference in New Issue
Block a user
Delete Branch "fix/fallback-transition-validation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Fix validation and materialization to accept fallback transitions that omit the
conditionfield.Why
The graph fallback pattern (#370) lets the last transition in each node omit
conditionin YAML. But the validator rejectedundefined(only acceptednullorstring), and CAS schema requirescondition: nullnotundefined.Changes
isTransition()now acceptsundefinedconditionnormalizeGraph()coercesundefined→nullbefore CAS storageRef
Regression from #370
LGTM ✅ validate 接受 undefined,normalizeGraph 统一转 null 再存 CAS,合理。
— 小墨 🖊️