docs: action disabled/errorMessage/undoable + predicate scope + object-form screen wizard#2007
Merged
Merged
Conversation
…t-form screen wizard
Fills hand-written doc + authoring-skill gaps for capabilities that shipped but
were undocumented:
- actions.mdx: add `errorMessage`/`undoable` to the field table and feedback
list; add an "Evaluation context" subsection (predicates are bare CEL against
the record; `record.<field>` resolves identically on every surface; narrower
scope than record-alert's os.*); warn against `${…}`/`{…}`-wrapped predicates.
- flow.mdx: document the `screen` node's object-form mode (`objectName`/`mode`/
`recordId`/`defaults`/`idVariable`) and the atomic parent+child save / id
rebind that powers multi-step object-form wizards.
- skills/objectstack-ui: document `disabled` (CEL, greys vs `visible` hides),
`errorMessage`, `undoable`, and the bare-CEL `record.*` predicate convention,
with a worked Reassign example.
Docs/skill only; no shipped-package changes.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
documentation
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
1 participant
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.
Fills hand-written doc + authoring-skill gaps for action/flow capabilities
that shipped over the recent rounds but were undocumented. No code/spec change.
Changes
content/docs/protocol/objectui/actions.mdxerrorMessageandundoableto the interface field table and theConfirmation & Feedback list (with a worked Reassign example).
evaluated against the record;
record.<field>resolves identically on everysurface (
record_header,list_item, …) — narrower scope thanrecord-alert conditions (no
os.*).${…}/{…}-wrapped predicates.content/docs/guides/metadata/flow.mdxscreennode's object-form mode (objectName/mode/recordId/defaults/idVariable) and the atomic parent+child save / idrebind that powers multi-step object-form wizards (lead → account →
opportunity).
skills/objectstack-ui/SKILL.mddisabled(CEL; greys out vsvisiblewhich hides),errorMessage,undoable, and the bare-CELrecord.*predicate convention.Why now
These pair with the recently-merged action work (custom messages, undoable,
CEL
disabled/visible, object-form wizard) and theevaluateCondition fix
that made bare-CEL predicates actually evaluate. The docs/skill already taught
bare CEL correctly — this fills the coverage gaps (the new fields + the
evaluation scope), it does not correct a now-false claim.
🤖 Generated with Claude Code