SDK documentation on error handling #122
Conversation
✅ Deploy Preview for docsrestatedev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
||
| // Inside your handler throw terminal errors via: | ||
| throw new TerminalError("Something went wrong.", { errorCode: 13, cause: "Something caused this." }) |
There was a problem hiding this comment.
Do we expose the error codes as an enum from the SDK?
There was a problem hiding this comment.
Right, we indeed expose those 👍 I will adapt it
There was a problem hiding this comment.
Hmm the only ones we expose are: internal, journal_mismatch and protocol_violation... Maybe that is not really worth exposing or documenting? Since journal mismatch and protocol violations are not something the user code detects
There was a problem hiding this comment.
Yes, we shouldn't expose journal_mismatch or protocol_violation to the user. Maybe at some point we want to expose something like an UserErrorCode that is aligned with https://github.com/restatedev/restate/blob/ebf084cdfa2639e192911d90394fdcc0168eeefe/src/types/src/errors.rs#L21 in case users want to use error codes across SDKs. Then let's leave it as is for now.
Fixes #90
SDK docs on retry strategy of Restate.