mirror of https://github.com/temetro/temetro.git synced 2026-08-31 12:58:08 +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.3 KiB

Raw Blame History

coss Field

When to use

Accessible field wrappers with labels, descriptions, and errors.
Form control state wiring (invalid, required, touched/error messaging).

Install

npx shadcn@latest add @coss/field

Manual deps from docs:

npm install @base-ui/react

Canonical imports

import {
  Field,
  FieldDescription,
  FieldError,
  FieldLabel,
  FieldValidity,
} from "@/components/ui/field"
import { Input } from "@/components/ui/input"

Minimal pattern

<Field>
  <FieldLabel>Name</FieldLabel>
  <Input type="text" placeholder="Enter your name" />
  <FieldDescription>Visible on your profile</FieldDescription>
  <FieldError>Please enter a valid name</FieldError>
  <FieldValidity>
    {(validity) => (
      {validity.error && <p>{validity.error}</p>}
    )}
  </FieldValidity>
</Field>

Patterns from coss particles

Key patterns

Required field with error:

<Field name="email">
  <FieldLabel>Email *</FieldLabel>
  <Input type="email" required placeholder="name@company.com" />
  <FieldDescription>We'll never share your email.</FieldDescription>
  <FieldError>Please enter a valid email.</FieldError>
</Field>

Field wrapping an autocomplete:

<Field name="framework">
  <FieldLabel>Framework</FieldLabel>
  <Autocomplete items={items}>
    <AutocompleteInput placeholder="Search..." />
    <AutocompletePopup>
      <AutocompleteList>
        {(item) => <AutocompleteItem key={item.value} value={item}>{item.label}</AutocompleteItem>}
      </AutocompleteList>
    </AutocompletePopup>
  </Autocomplete>
  <FieldError />
</Field>

More examples

See p-field-1 through p-field-9 for required, disabled, error, validity, input-group, autocomplete, and combobox field patterns.

Common pitfalls

Rendering errors detached from the related control, breaking context.
Missing name in form flows, causing silent submit omissions.
Using field wrapper without corresponding label/description/error semantics.

Useful particle references

required field: p-field-2
disabled field: p-field-3
with error: p-field-4
with validity: p-field-5
input group: p-field-6
autocomplete field: p-field-7
combobox field: p-field-8
combobox multiple field: p-field-9
form composition references: p-form-1, p-form-2, p-input-group-24

2.3 KiB Raw Blame History