Skip to content

Conversation

@robluton
Copy link
Contributor

CleanShot 2025-11-14 at 13 35 07@2x

@robluton robluton requested a review from a team as a code owner November 14, 2025 19:35
@vercel
Copy link

vercel bot commented Nov 14, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
docs Ready Ready Preview Comment Nov 17, 2025 3:45pm

Copy link
Contributor

@formfcw formfcw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @robluton.

Let’s put this in the Interface Component > Props section and add the disabled property as well, since the two of them are bound together. Consider adding something like, "We recommend implementing these states …"

| `collection` | string | The current collection name. |
| `field` | uuid | The key of the field. |
| `primaryKey` | string | The current item's primary key. |
| `disabled` | boolean | Prevents editing and applies subdued colors to the field. |
Copy link
Contributor

@formfcw formfcw Nov 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's rephrase this, since it's something that extension authors must implement themselves. Something like this — feel free to adapt it.

Suggested change
| `disabled` | boolean | Prevents editing and applies subdued colors to the field. |
| `disabled` | boolean | If true, it should appear in subdued colors with disabled interaction. We recommend implementing it. |

| `field` | uuid | The key of the field. |
| `primaryKey` | string | The current item's primary key. |
| `disabled` | boolean | Prevents editing and applies subdued colors to the field. |
| `nonEditable` | boolean | Prevents editing while maintaining normal visual styling. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's rephrase this, since it's something that extension authors must implement themselves. Something like this — feel free to adapt it.

Suggested change
| `nonEditable` | boolean | Prevents editing while maintaining normal visual styling. |
| `nonEditable` | boolean | If true, the field will be disabled but retain its normal visual styling, with interaction elements hidden. We recommend implementing it. |

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants