Field intents
Example
<Field intent="field.email" id="email" name="email" />Choosing between neighbours
Find the row that describes your element, and use the intent on the right.
If it is
Use
An email address
field.emailthis pageUsernames or handles
field.text
Connections
Declared in the registry, both directions. Where an intent is used in your own code is something check and the gallery see; this site has no app code.
- Built from
For registry authors
Starter intents. These are the intents prongs add puts in your registry, shown in this site’s theme. Yours are your own registry.ts: rename, restyle and add to them, and see them with prongs add gallery.
What this intent is built from and its entry in components/prongs/registry.ts. You only need this to change how it looks or to add an intent like it.
How field.email resolves, and its definition
Each layer adds to the one before it; a later class wins over an earlier one that sets the same thing.
input.defaultBordered input box
w-full min-w-0 rounded-md border border-input bg-background pl-3 pr-3 py-2 text-base text-foreground placeholder:text-muted-foreground focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring disabled:cursor-not-allowed disabled:opacity-50 aria-invalid:border-destructive
field.emailAn email address
w-full min-w-0 rounded-md border border-input bg-background pl-3 pr-3 py-2 text-base text-foreground placeholder:text-muted-foreground focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring disabled:cursor-not-allowed disabled:opacity-50 aria-invalid:border-destructive
{ type: 'email', inputMode: 'email', autoComplete: 'email' }'field.email': {
kind: 'semantic',
description: 'An email address',
refs: ['input.default'],
binding: {
behavior: { type: 'email', inputMode: 'email', autoComplete: 'email' },
},
notFor: [{ context: 'usernames or handles', instead: 'field.text' }],
},