feat: CEL disabled on action buttons + record-page Undo wiring#1787
Merged
Conversation
- components/layout (page header): evaluate CEL `disabled` against the record (was boolean-only), mirroring the existing `visible` eval — actions can grey out conditionally instead of only hiding. - plugin-grid RowActionMenu: evaluate `disabled` (boolean | CEL) per row item. - components action-button: forward `undoable`/`recordIdField` on execute. - app-shell RecordDetailView: mount useGlobalUndo + wire the success toast's "Undo" for undoable actions (prior values from the loaded record). - plugin-detail record:quick_actions: CEL disabled + running spinner per button. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
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.
What
Action UX follow-ups (the polish items from the prior round): evaluate a CEL
disabledpredicate on action buttons, and wire the record-page Undo affordance.CEL
disabledon action buttonsAction.disabledalready accepted a CEL predicate in the spec, but the renderers only honoured the boolean form (the CEL was silently ignored, likevisibleonce was). Now:components/layout/containers) evaluatesdisabledagainst the record — mirroring its existingvisibleeval. Verified: the CRM "Reassign Lead" header button greys out on a converted lead and is enabled otherwise.plugin-grid/RowActionMenu) evaluatesdisabledper row item (boolean or CEL against the row), and skips the click when disabled.plugin-detail) evaluatesdisabledper button and shows a running spinner.So an action can now grey out conditionally (
disabled) instead of only hiding (visible).Record-page Undo wiring
action-buttonnow forwardsundoable/recordIdFieldon execute (they were dropped, so undoable actions lost their Undo affordance through this path).RecordDetailViewmountsuseGlobalUndoand wires its success toast to offer "Undo" forundoableactions (capturing prior field values from the loaded record).Verification notes (honest)
disabledin the page header: browser-verified (greyed Reassign on a converted lead; enabled on a new lead).disabledin the row menu and the record-page Undo wiring: code-complete and mirror existing, verified patterns (the row-menuvisibleeval; the list-path Undo shipped earlier), but not re-driven end-to-end this session due to grid hover/menu flakiness in the harness.Only the example's "Reassign Lead" action declares a non-boolean
disabled, so the new evaluation has no effect on existing actions.🤖 Generated with Claude Code