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.
locate-character
Get the line and column number of a particular character in a string.
Installation
npm install locate-character, or get it from unpkg.com/locate-character.
Usage
To search for a particular character, using the index or a search string, use locate:
import { locate } from 'locate-character';
const sample = `
A flea and a fly in a flue
Were imprisoned, so what could they do?
Said the fly, "let us flee!"
"Let us fly!" said the flea.
So they flew through a flaw in the flue.
`.trim();
// Using a character index
const index = sample.indexOf('fly');
locate(sample, index);
// -> { line: 0, column: 13, character: 13 }
// Using the string itself
locate(sample, 'fly');
// -> { line: 0, column: 13, character: 13 }
// Using the string with a start index
locate(sample, 'fly', { startIndex: 14 });
// -> { line: 2, column: 9, character: 76 }
If you will be searching the same string repeatedly, it's much faster if you use getLocator:
import { getLocator } from 'locate-character';
const locate = getLocator(sample);
let location = locate(13);
// -> { line: 0, column: 13, character: 13 }
location = locate('fly', { startIndex: location.character + 1 });
// -> { line: 2, column: 9, character: 76 }
location = locate('fly', { startIndex: location.character + 1 });
// -> { line: 3, column: 8, character: 104 }
In some situations (for example, dealing with sourcemaps), you need one-based line numbers:
getLocator(sample, { offsetLine: 1 });
locate(sample, { offsetLine: 1 });
There's also an offsetColumn option which is less useful in real-world situations.
License
MIT