fix(app-shell): remove the never-firing record-change option from the flow trigger picker (#3427)#2812
Merged
Conversation
…low trigger picker (#3427) The start-node trigger picker offered "Record changed (any)" (`record-change`), but the runtime routes it to the record-change trigger, which maps it to no hook — the flow binds yet never fires, so authoring it produced a silently-dead flow. Removed the option, and dropped `record-change` from the scope resolver's record/previous sets and the zh-CN labels. The create-or-update case is covered by `record-after-write`; a companion @objectstack/lint rule flags any hand-authored `record-change` at `os validate` time. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018939yJ413zG3irLzcTtqaa
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
os-zhuang
marked this pull request as ready for review
July 25, 2026 00:33
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.
Summary
Companion to objectstack-ai/objectstack#3427. The Studio flow designer's start-node trigger picker offered "Record changed (any)" (
record-change), but the runtime routes it to the record-change trigger, which maps it to no ObjectQL hook — so the flow binds yet never fires. Authoring it produced a silently-dead flow.Changes
All in
packages/app-shell/src/views/metadata-admin/:inspectors/flow-node-config.ts— removed therecord-changeoption from the triggerselect, and dropped it from theshowWhengates of the Object / Entry-condition fields.inspectors/flow-scope.ts— removedrecord-changefromRECORD_TRIGGER_TYPESandPREVIOUS_TRIGGER_TYPES.i18n.ts— removed the zh-CN label.The common "created or updated" case is covered by
record-after-write(already in the picker). A companion@objectstack/lintrule flags any hand-authoredrecord-changeatos validatetime, so the trap is closed on both the Studio and validation fronts.Tests
flow-node-config.test.ts— new assertion that the picker no longer offersrecord-change.Changeset
@object-ui/app-shell: patch.Generated by Claude Code