feat(studio): reference pickers for Action target (flow/page/view)#1835
Merged
Conversation
The Action editor's target was a free-text field for flow/modal/form types, so admins had to know and type exact metadata names. Resolve it from the matching metadata type instead: - useMetaOptions: generic name+label loader for any metadata type (generalises useObjectOptions). - ActionDefaultInspector: flow -> flow picker, modal -> page picker, form -> view picker; url/api stay free text. Out-of-catalog values are preserved as a '(not found)' option so nothing is silently dropped. Verified live: a flow-type action's 'Flow name' is now a dropdown of real flows with the current target resolved to its label. Co-Authored-By: Claude Opus 4.8 <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.
Summary
The Action editor's
targetwas a free-text field forflow/modal/formtypes — admins had to know and type exact metadata names. It now resolves against the matching metadata type:useObjectOptions).flow→ flow picker,modal→ page picker,form→ view picker;url/apistay free text. Out-of-catalog values are preserved as a "(not found)" option so nothing is silently dropped.Verification
Verified live: a
flow-type action's Flow name is now a dropdown of the real flows (current target resolved to its label; opening it lists all flows). Full metadata-admin test suite (274) passes.🤖 Generated with Claude Code