Skip to content

ActionParamDialog: honour the spec carry-over param declaration — render carried JSON params as read-only summaries (objectstack#11753 ruling, ui half) #6246

Description

@os-support-ai

UI half of the objectstack#11753 ruling (maintainer, 2026-08-25, verbatim 「同意」 on recommendation A; full record = objectstack#11753 comment 5404887360). Filed by PM session session_01KWRU3s15AJz7PGW7a7wdCh per the confirmed checklist. Parent: objectstack#11753 (tracking).

Blocked-by: objectstack-ai/objectstack#11992

Cross-repo unlock criterion: not "the spec PR merged" — the spec change must be installable here (the objectui refresh/pin flow has picked it up and the installed @objectstack/spec accepts the new key). Verify on the installed package before starting.

Content: ActionParamDialog renders a param that declares the spec carry-over key as a collapsed read-only summary — seeded from the row, submitted verbatim, no editing affordance. The permission-set Clone dialog is the exemplar: it returns to its two ordinary text inputs plus read-only summaries for the five carried facets (description, object_permissions, field_permissions, system_permissions, row_level_security, tab_permissionsmember_default's RLS is 17+ policy objects in one value, the case that motivated the ruling).

Acceptance criterion: a dialog-level test pins what Clone renders (the gap objectstack#11753 names — today only the send side is pinned); the send-side contract (objectstack#11703's pin 6: what the action submits) stays green unchanged.

Notes: the failure direction this closes is a hand-mangled-but-valid JSON blob cloning a permission set that grants MORE than its base, silently accepted — the renderer must leave no editing affordance on declared carry-over params, not merely style them.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions