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.
53 lines
1.9 KiB
JavaScript
53 lines
1.9 KiB
JavaScript
"use strict";
|
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
const utils_1 = require("../utils");
|
|
exports.default = (0, utils_1.createRule)('no-inline-styles', {
|
|
meta: {
|
|
docs: {
|
|
description: 'disallow attributes and directives that produce inline styles',
|
|
category: 'Best Practices',
|
|
recommended: false
|
|
},
|
|
schema: [
|
|
{
|
|
type: 'object',
|
|
properties: {
|
|
allowTransitions: {
|
|
type: 'boolean'
|
|
}
|
|
},
|
|
additionalProperties: false
|
|
}
|
|
],
|
|
messages: {
|
|
hasStyleAttribute: 'Found disallowed style attribute.',
|
|
hasStyleDirective: 'Found disallowed style directive.',
|
|
hasTransition: 'Found disallowed transition.'
|
|
},
|
|
type: 'suggestion'
|
|
},
|
|
create(context) {
|
|
const allowTransitions = context.options[0]?.allowTransitions ?? false;
|
|
return {
|
|
SvelteElement(node) {
|
|
if (node.kind !== 'html') {
|
|
return;
|
|
}
|
|
for (const attribute of node.startTag.attributes) {
|
|
if (attribute.type === 'SvelteStyleDirective') {
|
|
context.report({ loc: attribute.loc, messageId: 'hasStyleDirective' });
|
|
}
|
|
if (attribute.type === 'SvelteAttribute' && attribute.key.name === 'style') {
|
|
context.report({ loc: attribute.loc, messageId: 'hasStyleAttribute' });
|
|
}
|
|
if (!allowTransitions &&
|
|
attribute.type === 'SvelteDirective' &&
|
|
attribute.kind === 'Transition') {
|
|
context.report({ loc: attribute.loc, messageId: 'hasTransition' });
|
|
}
|
|
}
|
|
}
|
|
};
|
|
}
|
|
});
|