-
Notifications
You must be signed in to change notification settings - Fork 0
Rendering and Output
Diagnostic construction stays independent from presentation: the same data renders anywhere.
| Output | Renderer |
|---|---|
| Rich terminal | TerminalRenderer |
| Plain text | PlainRenderer |
| Compiler-style text | CompilerTextRenderer |
| JSON | JsonRenderer |
| Markdown | MarkdownRenderer |
HTML (html feature) |
HTML renderer |
| Audit transcript | AuditTranscriptRenderer |
| GitHub Actions / delta annotations |
GithubActionsRenderer, GithubActionsDeltaRenderer
|
| SARIF 2.1.0 | SarifRenderer |
use diagprint::render::{
AuditTranscriptRenderer, CompilerTextRenderer, GithubActionsDeltaRenderer,
GithubActionsRenderer, JsonRenderer, MarkdownRenderer, PlainRenderer,
Renderer, SarifRenderer, TerminalRenderer,
};The terminal renderer draws secondary labels differently so related context never looks like an extra primary failure. CI-specific output is covered on CI & Code Scanning.
File reports support size-based, hourly and daily rotation plus retention cleanup:
use diagprint::{RotationCadence, RotationPolicy};
let policy = RotationPolicy {
cadence: RotationCadence::Daily,
..Default::default()
};With the compression feature, reports can be written as gzip or Zstandard:
use diagprint::Compression;
// Compression::Gzip
// Compression::ZstdColours and themes, including the Cybercore palette, are on Themes & Documentation. color(false) always wins and disables ANSI styling.
🩺 diagprint · a Cybercore Tech project · MIT OR Apache-2.0
🏠 cybercoretech.net ·
✉️ dev@cybercoretech.net ·
🔒 security@ ·
💬 Discord ·
🐛 Issues ·
☕ Buy Me a Coffee
⚡ Start
- 📥 Installation
- 🚀 Quick Start
- 🧪 Examples
🧱 Build
📤 Ship
🔧 Fix
- 🔧 Remediation
- 🛡️ Safety Model
🔬 Investigate
🛠️ Project
- 🛠️ Contributing
- 🗺️ Roadmap