VVibeFlui

Status Resolution

VibeFlui resolves operation feedback with resolveBackendFeedbackStatus.

The resolver searches for a feedback record in the given source, including nested data and HTTP-client-style response.data objects.

Boolean status

JSON
{ "status": true, "code": 200, "message": "Saved." }

status: true resolves to success.

JSON
{ "status": false, "code": 422, "message": "Email is already registered." }

status: false resolves by code:

  • 400..499 becomes warning.
  • Everything else becomes error.

String status

When status is a string, VibeFlui normalizes known values:

String statusFeedback status
"success", "succeeded", "ok", "accepted"success
"warning", "rejected"warning
"failed", "failure", "fail", "error"error
JSON
{ "status": "rejected", "message": "Manager approval is required." }

Unknown string statuses fall through to code when a code is present, then to the caller's fallback status.

Code-only status

If status is missing but code exists:

  • 200..299 becomes success.
  • 400..499 becomes warning.
  • 500+ becomes error.
JSON
{
  "code": "202",
  "message": "Export queued."
}

String numbers are parsed when possible.

Fallback status

When no explicit feedback status can be resolved, VibeFlui uses the caller's fallback:

  • Successful form submit and successful actions use success.
  • Caught errors use error.