8839075805
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>
44 lines
1.9 KiB
JavaScript
44 lines
1.9 KiB
JavaScript
import '../utils/dataTransfer/Clipboard.js';
|
|
import { readNextDescriptor } from '../utils/keyDef/readNextDescriptor.js';
|
|
|
|
/**
|
|
* Parse key definitions per `keyboardMap`
|
|
*
|
|
* Keys can be referenced by `{key}` or `{special}` as well as physical locations per `[code]`.
|
|
* Everything else will be interpreted as a typed character - e.g. `a`.
|
|
* Brackets `{` and `[` can be escaped by doubling - e.g. `foo[[bar` translates to `foo[bar`.
|
|
* Keeping the key pressed can be written as `{key>}`.
|
|
* When keeping the key pressed you can choose how long (how many keydown and keypress) the key is pressed `{key>3}`.
|
|
* You can then release the key per `{key>3/}` or keep it pressed and continue with the next key.
|
|
*/ function parseKeyDef(keyboardMap, text) {
|
|
const defs = [];
|
|
do {
|
|
const { type, descriptor, consumedLength, releasePrevious, releaseSelf = true, repeat } = readNextDescriptor(text, 'keyboard');
|
|
var _keyboardMap_find;
|
|
const keyDef = (_keyboardMap_find = keyboardMap.find((def)=>{
|
|
if (type === '[') {
|
|
var _def_code;
|
|
return ((_def_code = def.code) === null || _def_code === undefined ? undefined : _def_code.toLowerCase()) === descriptor.toLowerCase();
|
|
} else if (type === '{') {
|
|
var _def_key;
|
|
return ((_def_key = def.key) === null || _def_key === undefined ? undefined : _def_key.toLowerCase()) === descriptor.toLowerCase();
|
|
}
|
|
return def.key === descriptor;
|
|
})) !== null && _keyboardMap_find !== undefined ? _keyboardMap_find : {
|
|
key: 'Unknown',
|
|
code: 'Unknown',
|
|
[type === '[' ? 'code' : 'key']: descriptor
|
|
};
|
|
defs.push({
|
|
keyDef,
|
|
releasePrevious,
|
|
releaseSelf,
|
|
repeat
|
|
});
|
|
text = text.slice(consumedLength);
|
|
}while (text)
|
|
return defs;
|
|
}
|
|
|
|
export { parseKeyDef };
|