Components Common Mistakes
Passing a raw schema to a leaf component
FluiKit accepts FluiKitConfig and normalizes it before rendering.
Leaf components such as FluiKitForm, FluiKitTable, FluiKitField, FluiKitAction, FluiKitDetail, and FluiKitDashboard expect NormalizedFluiKitConfig.
Use normalizeSchema(schema) before direct usage.
Forgetting FluiKitProvider
Without FluiKitProvider, custom registry entries are unavailable.
This affects:
- custom components
- table and detail renderers
- field adapters
- validators
- transformers
- action handlers
- providers
- permissions
- option loaders
- hooks
- events
- message resolvers
- class name resolvers
- computed resolvers
Expecting plugin installation from adapter
Schema adapter and theme.preset do not install React components or third-party field adapters.
Use FluiKitProvider plugins or registry entries for actual runtime behavior.
Rendering modal or drawer on the server
FluiKitModal and FluiKitDrawer return null when document is unavailable.
Docs previews using these surfaces should run as client components.
Expecting action callbacks to always replace execution
Create and update callbacks replace built-in create/update execution in FluiKit.
Delete, row action, and bulk action callbacks can receive a result from built-in action execution when the table's execute flags are enabled.
Use executeDeleteAction, executeRowActions, or executeBulkActions when composing FluiKitTable directly.
Assuming every schema property affects the core component
Some schema properties are metadata for adapters or plugins. Component docs focus on behavior available in the current VibeFlui source.