dtoro
d4d99a7473
Problem: the hexagonal refactor churns the backend tree for nine more phases; the UI delivery stack (web/ SPA, cmd/desktop Wails wrapper, compose/web image) must move to its own repo first so doc/layout rewrites land once on a backend-only tree. Change: - New repo git.hubris.network/dtoro/oikos-web (v0.33.0): web/, desktop/ (updateURL repointed to oikos-web releases), compose/, own CI (web + desktop jobs), own deploy script (CI-green gate, TOCTOU guard, version-tagged images, prune-to-3), own webhook receiver on :9798 + launchd unit, own compose project publishing the same 8091:80. - Cutover executed on mac-mini in order: oikos stack's web service stopped+removed, oikos-web project brought up on 8091; outer Caddy untouched (targets the published port) — serving + Authentik flow + /wails 404 quirk verified post-cutover. - Stripped from oikos: web/, cmd/desktop/, compose/web/, desktop CI workflow, ci.yml web job, Makefile ui/desktop/desktop-package/install targets, the compose web service, oikos-web from deploy.sh's fallback prune list; wails + go-keyring dropped from go.mod, vendor synced. - README / CONTRIBUTING / AGENTS.md / .agents dev+operations docs now point at the new repo; mbse + mascot design docs carry a path note. Risk: production SPA serving depends on the new pipeline now; rollback is versioned-image re-up of the old web service from a pre-split checkout (port 8091). Desktop builds installed before the split still check dtoro/oikos releases — one manual reinstall, noted in the oikos-web release notes. Verification: go vet, make test (race), make generate-check, golangci (no new findings; baseline down 400→365); post-cutover curls — localhost:8091 200, /wails/runtime.js 404, outer Caddy 302 Authentik.
34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
Utilities for determining whether characters belong to character classes defined
|
|
by the XML specs.
|
|
|
|
## Organization
|
|
|
|
It used to be that the library was contained in a single file and you could just
|
|
import/require/what-have-you the `xmlchars` module. However, that setup did not
|
|
work well for people who cared about code optimization. Importing `xmlchars`
|
|
meant importing *all* of the library and because of the way the code was
|
|
generated there was no way to shake the resulting code tree.
|
|
|
|
Different modules cover different standards. At the time this documentation was
|
|
last updated, we had:
|
|
|
|
* `xmlchars/xml/1.0/ed5` which covers XML 1.0 edition 5.
|
|
* `xmlchars/xml/1.0/ed4` which covers XML 1.0 edition 4.
|
|
* `xmlchars/xml/1.1/ed2` which covers XML 1.0 edition 2.
|
|
* `xmlchars/xmlns/1.0/ed3` which covers XML Namespaces 1.0 edition 3.
|
|
|
|
## Features
|
|
|
|
The "things" each module contains can be categorized as follows:
|
|
|
|
1. "Fragments": these are parts and pieces of regular expressions that
|
|
correspond to the productions defined in the standard that the module
|
|
covers. You'd use these to *build regular expressions*.
|
|
|
|
2. Regular expressions that correspond to the productions defined in the
|
|
standard that the module covers.
|
|
|
|
3. Lists: these are arrays of characters that correspond to the productions.
|
|
|
|
4. Functions that test code points to verify whether they fit a production.
|