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
Currently, Fault has this concept of a wrapper that has a message and a wrapper that is just a wrapper with metadata.
The wrappers that only provide metadata and do not provide a useful string message will show up in error chains like this:
<fctx>: <fctx>: account not found: <kind>: <fctx>: sql: no rows in result set
That's a lot of useless noise and is a tough sell despite the benefits of Fault decorators.
What's happening here is each decorator that only provides metadata has no information to return when Error() string is called. So they simply return their name in angle brackets.
So when a top-level Error method is called, and it joins together the entire error chain separated by : (as with most error libraries) you end up with a bunch of wrapper names in between the useful internal error messages.
The text was updated successfully, but these errors were encountered:
Currently, Fault has this concept of a wrapper that has a message and a wrapper that is just a wrapper with metadata.
The wrappers that only provide metadata and do not provide a useful string message will show up in error chains like this:
That's a lot of useless noise and is a tough sell despite the benefits of Fault decorators.
What's happening here is each decorator that only provides metadata has no information to return when
Error() string
is called. So they simply return their name in angle brackets.So when a top-level
Error
method is called, and it joins together the entire error chain separated by:
(as with most error libraries) you end up with a bunch of wrapper names in between the useful internal error messages.The text was updated successfully, but these errors were encountered: