aetos/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: repair cp1252-mangled em-dashes and ellipsis in the reference-app wiki
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source 
All four 06_reference_app pages round-tripped U+2014 (em-dash) and U+2026
(ellipsis) through cp1252 during earlier PowerShell edits; restored the
characters and regenerated the wiki HTML + MCP modules.
This commit is contained in:
Vishesh 'ironeagle' Bangotra
2026-10-20 23:48:08 +05:30
parent a7f0576f1d
commit 7f951f3fe7
13 changed files with 69 additions and 69 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
standards/src/wiki/06_reference_app/04_client_admin.md
View File

@@ -1,7 +1,7 @@
# Client Admin — the spec-driven frontend
# Client Admin — the spec-driven frontend
The client sample (`standards/src/templates/client/`) renders a full admin —
auth pages, resource lists, forms, detail views — **from the server's
The client sample (`standards/src/templates/client/`) renders a full admin —
auth pages, resource lists, forms, detail views — **from the server's
`openapi.yaml`**, driven entirely by the x- extension fields. There are no
hand-written screens per resource.
@@ -9,10 +9,10 @@ hand-written screens per resource.
A Vite + React + MUI app wiring the two Aetos packages:
- **`@aetoskia/react-openapi`** — fetches `${VITE_API_BASE_URL}/openapi.json`,
- **`@aetoskia/react-openapi`** — fetches `${VITE_API_BASE_URL}/openapi.json`,
builds the router and the resource admin from the spec's schemas and x-
fields (list columns, autocomplete, fk pickers, enum selects, hidden fields…)
- **`@aetoskia/react-auth`** — login/register/logout against the auth-server
fields (list columns, autocomplete, fk pickers, enum selects, hidden fields…)
- **`@aetoskia/react-auth`** — login/register/logout against the auth-server
paths declared in the spec's `securitySchemes.bearerAuth`, and attaches the
JWT to every API call
- a shared MUI theme (`src/shared-theme/`) and the shell
@@ -40,7 +40,7 @@ npm run dev
Open the dev-server URL; the admin lists Parents, Pets, Treatments, Vets,
Appointments and Jobs straight from the vet spec. Edit `openapi.yaml` on the
server and the client follows on reload — the spec is the contract on both
server and the client follows on reload — the spec is the contract on both
sides.
## Where the x- extensions come from