@aryanjnyc Thanks for writing this blog. My question to you is why are you returning the error instead of throwing it to the caller function?
Oh my. Good catch. There's no reason for it and, in fact, that's definitely wrong. That should be a throw.
@aryanjnyc Thanks for making the update! I do apologize that the documentation we had was incorrect.
Ah, I actually found the root of my error. This serverErrorHandler is heavily inspired by existing Sentry docs that were recently changed. Here is the change this all stemmed from: github.com/getsentry/sentry-docs/c...
serverErrorHandler
Either way, yeah, good find! Thanks a bunch. I also updated my pull request to the Sentry docs: github.com/getsentry/sentry-docs/p...
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
@aryanjnyc Thanks for writing this blog. My question to you is why are you returning the error instead of throwing it to the caller function?
Oh my. Good catch. There's no reason for it and, in fact, that's definitely wrong. That should be a throw.
@aryanjnyc Thanks for making the update! I do apologize that the documentation we had was incorrect.
Ah, I actually found the root of my error. This
serverErrorHandleris heavily inspired by existing Sentry docs that were recently changed. Here is the change this all stemmed from: github.com/getsentry/sentry-docs/c...Either way, yeah, good find! Thanks a bunch. I also updated my pull request to the Sentry docs: github.com/getsentry/sentry-docs/p...