check-error-handling

You can enforce Rust error handling by validating the AppResult/AppError pattern and detecting regressions in anyhow usage. This ensures specific ErrorCode enums are utilized appropriately across the codebase.

The best way to check for anyhow usage is running pattern matching with ripgrep in source files. This detects regressions and prevents the reintroduction of the anyhow crate for error handling.

To validate AppResult and AppError types before merging, run a comprehensive error handling check in the project root directory. This guarantees compliance with established error handling standards and prevents common pitfalls.

Yes, Rust error handling validation requires ripgrep for pattern matching within source files. This dependency is necessary to enforce the AppResult/AppError pattern and check ErrorCode enum utilization.

You should use AppResult instead of anyhow to ensure consistent, robust error management across your codebase. Validating this pattern prevents regressions and enforces strict error handling standards with ErrorCode enums.

You need to check ErrorCode enum utilization when modifying error handling logic before a pull request. This verifies that specific error codes are used appropriately and maintains unified AppError types.