Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define failure cases within bobtimus that are worthwhile reporting to the frontend #229

Open
1 task
thomaseizinger opened this issue Aug 7, 2021 · 1 comment

Comments

@thomaseizinger
Copy link
Contributor

thomaseizinger commented Aug 7, 2021

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:

  1. Identify, which concrete errors we want to know about on the frontend.
  2. 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.)
  3. Define and use error types for this within bobtimus (i.e. structs that implement std::error::Error)
  4. Define a mapping of these errors to the specified error format
  5. Write the error handling code for the errors on the frontend

Failure cases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants