Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Contributing

Development setup and broad contribution guidance live in the repository CONTRIBUTING.md. This page records contributor-facing implementation notes that should stay visible in the rendered docs.

Crash-log correlation follow-ups

The crash-log correlation implementation is intentionally conservative: it parses Crash Logger SSE, Trainwreck, and generic logs, then correlates mentioned plugins, DLLs, assets, and form IDs with modde’s local install database. The public framing must stay narrow: existing analyzers and MO2/Vortex integrations already exist, while modde’s edge is correlating crash evidence with the managed profile, installed files, plugin order, versions, Nexus metadata, and experiment state.

The parser section names were checked against upstream source instead of invented fixtures:

The remaining missing pieces are:

Missing pieceWhy it is requiredUpstream/source to provide itValidation command
Sanitized real Crash Logger SSE fixture logsParser behavior should be locked against real log shape, not synthetic examplesA contributor with permission to share redacted Crash Logger SSE logsnix develop . -c cargo test -p modde-core crash_logger
Sanitized real Trainwreck fixture logsTrainwreck-specific parsing needs real-world coverage before broad compatibility claimsA contributor with permission to share redacted Trainwreck logsnix develop . -c cargo test -p modde-core trainwreck
CLI text and JSON snapshot tests for modde doctor crashThe command output is user-facing and should not drift accidentallyAdd fixtures under the CLI test fixture tree once real logs are availablenix develop . -c cargo test -p modde crash
Correlation matrix testsPlugin, DLL, asset, no-match, disabled-mod, and inactive-profile cases need regression coverageLocal test databases built from sanitized fixture manifestsnix develop . -c cargo test -p modde-core crash::
UI diagnostics crash-log testsImport state and rendered suspect rows need coverage in the Iced diagnostics viewUI simulator tests using sanitized local fixture pathsnix develop . -c cargo test -p modde-ui diagnostics
Full workspace verification after CLI async recursion is fixedCurrent full CLI/workspace checks are blocked by unrelated deploy/patcher async recursionFix the recursion between crates/modde-cli/src/commands/deploy.rs and crates/modde-cli/src/commands/patcher.rsnix develop . -c cargo test --workspace

Do not replace the fixture requirement with generated crash logs. If a fixture is missing, report the exact fixture set needed and the validation command above.