Improve handling of errors #39

New Issue

Jef Roosens · 2021-04-22T10:14:52Z

Jef Roosens commented

2021-04-22 10:14:52 +00:00

At the moment, we just convert every type of error into a FejError object, but this approaches isn't as flexible when it comes to defining verbose error messages.

As an alternative, could define FejError like this:

pub enum FejError {
	ReqwestError(reqwest::Error),
    DatabaseError(diesel::result::Error),
}

We can then define a From<reqwest::Error> for Status for each wrapped type (reqwest::Error is just an example here). This way, we have full control over what each error represents when returning a Status.

As a bonus, we can practice writing macros, as this looks like a prime example.

Inspiration for this approach

At the moment, we just convert every type of error into a `FejError` object, but this approaches isn't as flexible when it comes to defining verbose error messages. As an alternative, could define `FejError` like this: ```rust pub enum FejError { ReqwestError(reqwest::Error), DatabaseError(diesel::result::Error), } ``` We can then define a `From<reqwest::Error> for Status` for each wrapped type (`reqwest::Error` is just an example here). This way, we have full control over what each error represents when returning a Status. As a bonus, we can practice writing macros, as this looks like a prime example. [Inspiration for this approach](https://edgarluque.com/blog/wrapping-errors-in-rust)

Jef Roosens added this to the Fej 1.1.1 milestone 2021-04-22 10:14:52 +00:00

Jef Roosens added the

enhancement

label 2021-04-22 10:14:52 +00:00

Jef Roosens self-assigned this 2021-04-22 10:14:52 +00:00

Jef Roosens added this to the Fej 1.1.1 project 2021-04-22 10:14:52 +00:00

Jef Roosens modified the milestone from Fej 1.1.1 to Fej 1.1.0 - The Calm before the Storm

2021-04-22 10:19:51 +00:00

Jef Roosens modified the project from Fej 1.1.1 to Fej 1.1.0

2021-04-22 10:19:53 +00:00

Jef Roosens added the

project/backend