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
All AybErrors are of one type with a message, which makes it hard to handle them programatically. Consider making each error have its own type and/or use an enum for them.
Referencing the wrong entity results in Error: RowNotFound
From implementation in https://github.com/marcua/ayb/blob/main/src/error.rs translates the text of the errors, but doesn't show the example. e.g., AddressError says an email address was parsed wrong, but was it the to/from/reply_to? What was the actual email that wasn't valid?
Better utilize actix's error handling functionality with typed AybErrors to modify return types (e.g., return 403/Forbidden on permissions errors, etc.)
The text was updated successfully, but these errors were encountered:
marcua
changed the title
More helpful error messages
More helpful errors
Oct 29, 2023
AybError
s are of one type with amessage
, which makes it hard to handle them programatically. Consider making each error have its own type and/or use an enum for them.Error: RowNotFound
From
implementation in https://github.com/marcua/ayb/blob/main/src/error.rs translates the text of the errors, but doesn't show the example. e.g., AddressError says an email address was parsed wrong, but was it the to/from/reply_to? What was the actual email that wasn't valid?AybError
s to modify return types (e.g., return 403/Forbidden on permissions errors, etc.)The text was updated successfully, but these errors were encountered: