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.
36 lines
999 B
Markdown
36 lines
999 B
Markdown
# Validate XML Names and Qualified Names
|
|
|
|
This package simply tells you whether or not a string matches the [`Name`](http://www.w3.org/TR/xml/#NT-Name) or [`QName`](http://www.w3.org/TR/xml-names/#NT-QName) productions in the XML Namespaces specification. We use it for implementing the [validate](https://dom.spec.whatwg.org/#validate) algorithm in jsdom, but you can use it for whatever you want.
|
|
|
|
## Usage
|
|
|
|
This package's main module exports two functions, `name()` and `qname()`. Both take a string and return a boolean indicating whether or not the string matches the relevant production.
|
|
|
|
```js
|
|
"use strict":
|
|
const xnv = require("xml-name-validator");
|
|
|
|
// Will return true
|
|
xnv.name("x");
|
|
xnv.name(":");
|
|
xnv.name("a:0");
|
|
xnv.name("a:b:c");
|
|
|
|
// Will return false
|
|
xnv.name("\\");
|
|
xnv.name("'");
|
|
xnv.name("0");
|
|
xnv.name("a!");
|
|
|
|
// Will return true
|
|
xnv.qname("x");
|
|
xnv.qname("a0");
|
|
xnv.qname("a:b");
|
|
|
|
// Will return false
|
|
xnv.qname(":a");
|
|
xnv.qname(":b");
|
|
xnv.qname("a:b:c");
|
|
xnv.qname("a:0");
|
|
```
|