Feedback Config
Type: FluiKitFeedbackConfig.
Properties
| Property | Type | Required | Default | Description |
|---|---|---|---|---|
enabled | boolean | No | true | Enables operation feedback. |
mode | "inline" | "modal" | No | "modal" | Feedback display mode. |
icons | { success?: string; error?: string; warning?: string } | No | { success: "mdi:check-circle-outline", error: "mdi:alert-circle-outline", warning: "mdi:alert-outline" } | Feedback icon map. |
className | string | No | - | Feedback class name. |
Statuses
UI feedback status type:
TS
type FluiKitFeedbackStatus = "success" | "error" | "warning";Backend/action responses can use boolean status, recognized string status, or code-only fallback. A response with status: false and a 400..499 code resolves to warning feedback; string statuses such as "rejected", "accepted", and "failed" resolve to warning, success, and error respectively.
Feedback reflects what the frontend observed, not an independent backend guarantee. If an action or form submission completes with no handler, provider, or endpoint resolved to interpret a response from, VibeFlui displays success feedback assuming the operation completed, because VibeFlui only handles the FE/UI layer and is not responsible for backend results. See Action Config: No-op behavior.
Example
TS
feedback: {
enabled: true,
mode: "modal",
icons: {
success: "lucide:circle-check",
error: "lucide:circle-x",
warning: "lucide:triangle-alert"
}
}