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>
45 lines
1.4 KiB
TypeScript
45 lines
1.4 KiB
TypeScript
import { GMT, Weekday } from './index';
|
|
/**
|
|
* Only the first parameter is mandatory. Either the second, the third, or both
|
|
* may be left out.
|
|
*
|
|
* If only one parameter is present, the function yeilds a true value on the
|
|
* weekday that the parameter represents. If the string "GMT" is specified as
|
|
* a second parameter, times are taken to be in GMT, otherwise in local timezone.
|
|
*
|
|
* If both wd1 and wd1 are defined, the condition is true if the current weekday
|
|
* is in between those two weekdays. Bounds are inclusive. If the "GMT" parameter
|
|
* is specified, times are taken to be in GMT, otherwise the local timezone is
|
|
* used.
|
|
*
|
|
* Valid "weekday strings" are:
|
|
*
|
|
* SUN MON TUE WED THU FRI SAT
|
|
*
|
|
* Examples:
|
|
*
|
|
* ``` js
|
|
* weekdayRange("MON", "FRI")
|
|
* true Monday trhough Friday (local timezone).
|
|
*
|
|
* weekdayRange("MON", "FRI", "GMT")
|
|
* same as above, but GMT timezone.
|
|
*
|
|
* weekdayRange("SAT")
|
|
* true on Saturdays local time.
|
|
*
|
|
* weekdayRange("SAT", "GMT")
|
|
* true on Saturdays GMT time.
|
|
*
|
|
* weekdayRange("FRI", "MON")
|
|
* true Friday through Monday (note, order does matter!).
|
|
* ```
|
|
*
|
|
*
|
|
* @param {String} wd1 one of the weekday strings.
|
|
* @param {String} wd2 one of the weekday strings.
|
|
* @param {String} gmt is either the string: GMT or is left out.
|
|
* @return {Boolean}
|
|
*/
|
|
export default function weekdayRange(wd1: Weekday, wd2?: Weekday | GMT, gmt?: GMT): boolean;
|
|
//# sourceMappingURL=weekdayRange.d.ts.map
|