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
Thanks to Chronos v4 supports proper raises tracking, it now makes more sense to use exception tracking and specifically also custom errors to correctly signal error types.
I have a custom error type, that I have correctly added to raises and created for it specific Result type like this:
Then I got an error from Nim that points out that the raised error is ref CatchableError type and not ref SubscriptionError. If I use the Result's API directly, then the expected error is correctly ref SubscriptionError
The text was updated successfully, but these errors were encountered:
Thanks to Chronos v4 supports proper
raises
tracking, it now makes more sense to use exception tracking and specifically also custom errors to correctly signal error types.I have a custom error type, that I have correctly added to
raises
and created for it specificResult
type like this:When I used it with Questionable like this:
Then I got an error from Nim that points out that the raised error is
ref CatchableError
type and notref SubscriptionError
. If I use the Result's API directly, then the expected error is correctlyref SubscriptionError
The text was updated successfully, but these errors were encountered: