Schema Metadata
Admin UI and tooling can fetch schema metadata:
http
GET /meta/schema1
- Returns a JSON model registry derived from
schema.tsand platform models - Includes table names, fields, relationships, validation rules, and UI config
- Each model's
uicarries the schema'sui.listView(ornullif not declared); the admin UI renders exactly those columns, in order — timestamps included - Each model's
accesscarries the schema's access-rule strings per operation (e.g."admin|manager","authenticated","system"); the admin UI uses them to hide mutation controls the signed-in role can't use. Cosmetic only — the server enforces regardless; rules not expressible as strings serialize asnull - Semi‑protected route: accepts optional auth; sensitive fields are omitted by design
Raw schema in dev
- In development, the raw
schema.tsis also served for convenience:
http
GET /schema.ts1
- The runtime resolves the service’s
schema.tswith multiple fallback paths so Admin UI and tools can auto‑discover it.
Use cases
- Drive dynamic admin forms, lists, and references
- Power external tooling or validators that prefer working from raw TS schema