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>
72 lines
1.9 KiB
Markdown
72 lines
1.9 KiB
Markdown
# recursive-readdir
|
|
|
|
[](https://travis-ci.org/jergason/recursive-readdir)
|
|
|
|
Recursively list all files in a directory and its subdirectories. It does not list the directories themselves.
|
|
|
|
Because it uses fs.readdir, which calls [readdir](http://linux.die.net/man/3/readdir) under the hood
|
|
on OS X and Linux, the order of files inside directories is [not guaranteed](http://stackoverflow.com/questions/8977441/does-readdir-guarantee-an-order).
|
|
|
|
## Installation
|
|
|
|
npm install recursive-readdir
|
|
|
|
## Usage
|
|
|
|
```javascript
|
|
var recursive = require("recursive-readdir");
|
|
|
|
recursive("some/path", function (err, files) {
|
|
// `files` is an array of file paths
|
|
console.log(files);
|
|
});
|
|
```
|
|
|
|
It can also take a list of files to ignore.
|
|
|
|
```javascript
|
|
var recursive = require("recursive-readdir");
|
|
|
|
// ignore files named "foo.cs" or files that end in ".html".
|
|
recursive("some/path", ["foo.cs", "*.html"], function (err, files) {
|
|
console.log(files);
|
|
});
|
|
```
|
|
|
|
You can also pass functions which are called to determine whether or not to
|
|
ignore a file:
|
|
|
|
```javascript
|
|
var recursive = require("recursive-readdir");
|
|
|
|
function ignoreFunc(file, stats) {
|
|
// `file` is the path to the file, and `stats` is an `fs.Stats`
|
|
// object returned from `fs.lstat()`.
|
|
return stats.isDirectory() && path.basename(file) == "test";
|
|
}
|
|
|
|
// Ignore files named "foo.cs" and descendants of directories named test
|
|
recursive("some/path", ["foo.cs", ignoreFunc], function (err, files) {
|
|
console.log(files);
|
|
});
|
|
```
|
|
|
|
## Promises
|
|
You can omit the callback and return a promise instead.
|
|
|
|
```javascript
|
|
var recursive = require("recursive-readdir");
|
|
|
|
recursive("some/path").then(
|
|
function(files) {
|
|
console.log("files are", files);
|
|
},
|
|
function(error) {
|
|
console.error("something exploded", error);
|
|
}
|
|
);
|
|
```
|
|
|
|
The ignore strings support Glob syntax via
|
|
[minimatch](https://github.com/isaacs/minimatch).
|