You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow-up issue based on the findings here: #196 (comment)
The infrastructure of good error reporting is in place, i.e. we have a well-defined error interface through RFC7807.
To make use of this, we need to:
Identify, which concrete errors we want to know about on the frontend.
Design the error response we would like to see for these errors. In other words, think about the RFC7807 response first. (Bonus points for adding tests for it.)
Define and use error types for this within bobtimus (i.e. structs that implement std::error::Error)
Define a mapping of these errors to the specified error format
Write the error handling code for the errors on the frontend
This is a follow-up issue based on the findings here: #196 (comment)
The infrastructure of good error reporting is in place, i.e. we have a well-defined error interface through RFC7807.
To make use of this, we need to:
struct
s that implementstd::error::Error
)Failure cases
The text was updated successfully, but these errors were encountered: