mirror of https://github.com/temetro/temetro.git synced 2026-08-31 04:47:57 +00:00

Files

T

Khalid Abdi 929bec8f31 feat: AI-added records save with placeholders + "Added by AI" provenance

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>

2026-06-14 19:27:17 +03:00

2.1 KiB

Raw Blame History

coss Alert

When to use

Inline status messaging in content flows.
Semantic feedback variants (info, success, warning, error) with optional icons and actions.

When NOT to use

If the message is transient and should auto-dismiss -> use Toast instead.
If the message requires user action before proceeding -> use AlertDialog instead.
If it's a brief hover hint -> use Tooltip instead.

Install

npx shadcn@latest add @coss/alert

Manual deps from docs:

# No extra runtime dependency required for this primitive.

Canonical imports

import { Alert, AlertAction, AlertDescription, AlertTitle } from "@/components/ui/alert"

Minimal pattern

<Alert>
  <AlertTitle>Heads up!</AlertTitle>
  <AlertDescription>
    You can add components and dependencies to your app using the cli.
  </AlertDescription>
</Alert>

Patterns from coss particles

Key patterns

Alert with semantic icon (do NOT use aria-hidden — icon conveys status):

<Alert variant="info">
  <InfoIcon />
  <AlertTitle>Heads up!</AlertTitle>
  <AlertDescription>You can add components using the CLI.</AlertDescription>
</Alert>

Variants: default, info, success, warning, error.

Alert with action buttons (use AlertAction):

<Alert>
  <InfoIcon />
  <AlertTitle>Heads up!</AlertTitle>
  <AlertDescription>Describe what can be done about it here.</AlertDescription>
  <AlertAction>
    <Button size="xs" variant="ghost">Dismiss</Button>
    <Button size="xs">Ok</Button>
  </AlertAction>
</Alert>

More examples

See p-alert-1 through p-alert-7 for all variants and action patterns.

Common pitfalls

Using alert variants for passive decoration instead of meaningful semantic status.
Missing title/description structure in complex alerts, reducing scannability.
Hiding semantic alert icons with aria-hidden when they convey status meaning.

Useful particle references

with icon: p-alert-2
with icon and action buttons: p-alert-3
info alert: p-alert-4
success alert: p-alert-5
warning alert: p-alert-6
error alert: p-alert-7

2.1 KiB Raw Blame History