Registries
Field, view, and component registries — how the admin resolves renderers from schema.
Registries are the mechanism that connects server-side schema to client-side rendering. When the admin panel encounters a text field, it looks up the text renderer in the field registry.
How Registries Work
Rendering diagram...
Field Registry
Maps field types to React components:
| Field type | Renderer |
|---|---|
text | TextInput |
textarea | TextareaInput |
richText | RichTextEditor (TipTap) |
number | NumberInput |
boolean | Checkbox / Switch |
date | DatePicker |
datetime | DateTimePicker |
select | SelectDropdown |
relation | RelationPicker |
upload | FileUpload |
object | NestedForm |
array | RepeatableItems |
blocks | BlockEditor |
json | JSONEditor |
View Registry
Maps view types to React components:
| View type | Renderer |
|---|---|
table | TableView (list) |
form | FormView (edit) |
Component Registry
General-purpose component registry for dynamic rendering:
| Component type | Renderer |
|---|---|
icon | IconComponent |
badge | BadgeComponent |
Extending Registries
Register custom renderers by placing files in the admin directory. Codegen discovers them automatically:
Rendering diagram...
These are merged with built-in defaults during codegen and exported in .generated/client.ts.
Related Pages
- Custom Fields — Creating field types
- Custom Views — Creating view types
- Plugins — Plugin system