mirror of
https://github.com/temetro/temetro.git
synced 2026-08-25 09:56:56 +00:00
929bec8f31
Stop blocking AI imports/proposals on missing non-critical fields. Records the chat agent drafts now save with safe placeholders, auto-generated file numbers, and a source="ai" marker that surfaces an "Added by AI" badge so a clinician can review/edit them later. Backend: - add `source` (manual|ai) column to patients/appointments/prescriptions (migration 0014) + canonical types, services, validation schemas - relax patient/appointment validation: empty file number allowed, demographic + type/provider/initials fall back to placeholders (initials derived from name) - patients.generateFileNumber() auto-assigns an MRN when one is missing - proposeAppointment accepts a name when no file number resolves; AI commits + /api/ai/import stamp source="ai" Frontend: - `source` on Appointment/Patient/Prescription types; AI commits send source="ai" - reusable <AiBadge> shown on the Patients table/detail and prescriptions list Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.6 KiB
1.6 KiB
coss Empty
When to use
- No-data/no-results states with guidance.
- Action-oriented recovery UIs when content lists are empty.
Install
npx shadcn@latest add @coss/empty
Manual deps from docs:
# No extra runtime dependency required for this primitive.
Canonical imports
import {
Empty,
EmptyContent,
EmptyDescription,
EmptyHeader,
EmptyMedia,
EmptyTitle,
} from "@/components/ui/empty"
Minimal pattern
<Empty>
<EmptyHeader>
<EmptyMedia variant="icon">
<Icon />
</EmptyMedia>
<EmptyTitle>No data</EmptyTitle>
<EmptyDescription>No data found</EmptyDescription>
</EmptyHeader>
<EmptyContent>
<Button>Add data</Button>
</EmptyContent>
</Empty>
Patterns from coss particles
Key patterns
Empty state with icon and action:
<Empty>
<EmptyHeader>
<EmptyMedia variant="icon">
<FolderIcon aria-hidden="true" />
</EmptyMedia>
<EmptyTitle>No projects yet</EmptyTitle>
<EmptyDescription>Get started by creating your first project.</EmptyDescription>
</EmptyHeader>
<EmptyContent>
<Button>
<PlusIcon aria-hidden="true" />
New Project
</Button>
</EmptyContent>
</Empty>
Always include an actionable next step (button, link) in EmptyContent.
More examples
See p-empty-1 for the core pattern.
Common pitfalls
- Presenting empty states without actionable next step.
- Using empty state component for loading/error states instead of dedicated primitives.
- Copy-only empty states with no context-specific guidance for recovery.
Useful particle references
- core patterns:
p-empty-1