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.
31 lines
942 B
JavaScript
31 lines
942 B
JavaScript
"use strict";
|
|
|
|
module.exports = function ({ key, objectKey }) {
|
|
// special case for parsers
|
|
const isParser =
|
|
objectKey === "parser" && (key === "parse" || key === "parseForESLint");
|
|
const parserMessage = `
|
|
This typically happens when you're using a custom parser that does not
|
|
provide a "meta" property, which is how ESLint determines the serialized
|
|
representation. Please open an issue with the maintainer of the custom parser
|
|
and share this link:
|
|
|
|
https://eslint.org/docs/latest/extend/custom-parsers#meta-data-in-custom-parsers
|
|
`.trim();
|
|
|
|
return `
|
|
The requested operation requires ESLint to serialize configuration data,
|
|
but the configuration key "${objectKey}.${key}" contains a function value,
|
|
which cannot be serialized.
|
|
|
|
${
|
|
isParser
|
|
? parserMessage
|
|
: "Please double-check your configuration for errors."
|
|
}
|
|
|
|
If you still have problems, please stop by https://eslint.org/chat/help to chat
|
|
with the team.
|
|
`.trimStart();
|
|
};
|