error-handling

Error handling strategies involve classifying error sources, selecting appropriate error types like sentinel or custom wrapped errors, and defining propagation paths to preserve debugging context across service boundaries.

Propagating errors across boundaries requires contextual wrapping to preserve debugging information, mapping domain errors to transport-level responses, and documenting API contracts to ensure clear downstream handling.

Sentinel errors are used for clear downstream handling of specific expected conditions, while custom wrapped errors are used to propagate and enrich errors with contextual debugging information across package boundaries.

Mapping domain errors to transport responses is done at the boundary by translating internal error categories into appropriate transport-level responses and documenting these error contracts for the API surface.

Yes, the error handling approach applies to both library design and service boundary development by enforcing error categorization, propagation rules, and boundary mapping to handle errors gracefully across software packages.