tftsr-devops_investigation/node_modules/cssstyle/lib/properties/fontFamily.js
Shaun Arman 8839075805 feat: initial implementation of TFTSR IT Triage & RCA application
Implements Phases 1-8 of the TFTSR implementation plan.

Rust backend (Tauri 2.x, src-tauri/):
- Multi-provider AI: OpenAI-compatible, Anthropic, Gemini, Mistral, Ollama
- PII detection engine: 11 regex patterns with overlap resolution
- SQLCipher AES-256 encrypted database with 10 versioned migrations
- 28 Tauri IPC commands for triage, analysis, document, and system ops
- Ollama: hardware probe, model recommendations, pull/delete with events
- RCA and blameless post-mortem Markdown document generators
- PDF export via printpdf
- Audit log: SHA-256 hash of every external data send
- Integration stubs for Confluence, ServiceNow, Azure DevOps (v0.2)

Frontend (React 18 + TypeScript + Vite, src/):
- 9 pages: full triage workflow NewIssue→LogUpload→Triage→Resolution→RCA→Postmortem→History+Settings
- 7 components: ChatWindow, TriageProgress, PiiDiffViewer, DocEditor, HardwareReport, ModelSelector, UI primitives
- 3 Zustand stores: session, settings (persisted), history
- Type-safe tauriCommands.ts matching Rust backend types exactly
- 8 IT domain system prompts (Linux, Windows, Network, K8s, DB, Virt, HW, Obs)

DevOps:
- .woodpecker/test.yml: rustfmt, clippy, cargo test, tsc, vitest on every push
- .woodpecker/release.yml: linux/amd64 + linux/arm64 builds, Gogs release upload

Verified:
- cargo check: zero errors
- tsc --noEmit: zero errors
- vitest run: 13/13 unit tests passing

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
2026-03-14 22:36:25 -05:00

96 lines
2.4 KiB
JavaScript

"use strict";
const parsers = require("../parsers");
module.exports.parse = function parse(v) {
if (v === "") {
return v;
}
const keywords = [
"serif",
"sans-serif",
"cursive",
"fantasy",
"monospace",
"system-ui",
"math",
"ui-serif",
"ui-sans-serif",
"ui-monospace",
"ui-rounded"
];
const genericValues = ["fangsong", "kai", "khmer-mul", "nastaliq"];
const val = parsers.splitValue(v, {
delimiter: ","
});
const font = [];
let valid = false;
for (const i of val) {
const str = parsers.parseString(i);
if (str) {
font.push(str);
valid = true;
continue;
}
const key = parsers.parseKeyword(i, keywords);
if (key) {
font.push(key);
valid = true;
continue;
}
const obj = parsers.parseFunction(i);
if (obj) {
const { name, value } = obj;
if (name === "generic" && genericValues.includes(value)) {
font.push(`${name}(${value})`);
valid = true;
continue;
}
}
// This implementation does not strictly follow the specification.
// The spec does not require the first letter of the font-family to be
// capitalized, and unquoted font-family names are not restricted to ASCII.
// However, in the real world, the first letter of the ASCII font-family
// names are capitalized, and unquoted font-family names do not contain
// spaces, e.g. `Times`. And non-ASCII font-family names are quoted even
// without spaces, e.g. `"メイリオ"`.
// @see https://drafts.csswg.org/css-fonts/#font-family-prop
if (
i !== "undefined" &&
/^(?:[A-Z][A-Za-z\d-]+(?:\s+[A-Z][A-Za-z\d-]+)*|-?[a-z][a-z-]+)$/.test(i)
) {
font.push(i.trim());
valid = true;
continue;
}
if (!valid) {
return;
}
}
return font.join(", ");
};
module.exports.isValid = function isValid(v) {
if (v === "") {
return true;
}
return typeof module.exports.parse(v) === "string";
};
module.exports.definition = {
set(v) {
v = parsers.prepareValue(v, this._global);
if (parsers.hasVarFunc(v)) {
this._setProperty("font", "");
this._setProperty("font-family", v);
} else {
this._setProperty("font-family", module.exports.parse(v));
}
},
get() {
return this.getPropertyValue("font-family");
},
enumerable: true,
configurable: true
};