[QUALITY] Consistent error structure across all crate modules #23

Open
opened 2026-02-15 18:00:45 +00:00 by thabeta · 0 comments
Owner

The current src/error.rs provides a solid foundation for unified error handling. However, many modules are still reporting primitive errors or using disparate error types. This ticket tracks the refactor to ensure all modules (server, auth, db) consistently use the Error enum variants defined in src/error.rs and leverage the classification methods like .is_transient() and .is_fatal() for more robust error handling logic.

The current `src/error.rs` provides a solid foundation for unified error handling. However, many modules are still reporting primitive errors or using disparate error types. This ticket tracks the refactor to ensure all modules (server, auth, db) consistently use the `Error` enum variants defined in `src/error.rs` and leverage the classification methods like `.is_transient()` and `.is_fatal()` for more robust error handling logic.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
geomind_code/my_fs#23
No description provided.