VVibeFlui

Issue Reports

Good reports help maintainers reproduce the problem without guessing.

Bug report template

MD
## Summary

Describe the problem in one or two sentences.

## Environment

- VibeFlui package:
- VibeFlui version:
- React version:
- Next.js version:
- Adapter package:
- Browser:

## Expected behavior

What should happen?

## Actual behavior

What happens instead?

## Minimal schema

```ts
// Paste the smallest schema that reproduces the issue.
```

## Registry keys

```ts
// Paste only the registry entries involved in the issue.
```

## Data or response shape

```json
{
  "status": true,
  "code": 200,
  "message": "Example response"
}
```

## Reproduction steps

1. Open ...
2. Click ...
3. Observe ...

## Additional context

Screenshots, console errors, terminal output, or related notes.

Feature request template

MD
## Use case

What product workflow needs this?

## Current workaround

How are you handling it today?

## Proposed schema shape

```ts
// Optional: show the smallest schema shape you imagine.
```

## Runtime expectation

What should VibeFlui render or execute?

## Scope

Should this belong to core, an adapter, documentation, or an example?

Documentation issue template

MD
## Page

Link or path to the page.

## Problem

What is unclear, incomplete, or incorrect?

## Source check

If you checked the VibeFlui source, note the file or behavior you found.

## Suggested fix

What should the docs say instead?

What not to include

Do not include:

  • Access tokens.
  • Private API URLs.
  • Customer records.
  • Production database data.
  • Wallet private keys or seed phrases.
  • Screenshots that expose confidential data.