Error handling in query functions
Sometimes, when I write queries, I want to check if the user is authorized to reach that endpoint and if not I want to throw an error back to the user. But, I don't want this error to completely hijack the ui like it normally does, like with an error boundary. Sometimes, I just, say, want an additional UI to show up with the option for the user to sign in
I simply would like to have back the diversity of errors that regular http requests offer. I'm torn on how I'm supposed to implement errors for authentication, or authorization or some other error, and send that back to the frontend
3 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
How to throw errors with attached data: https://docs.convex.dev/functions/error-handling/application-errors.
You can catch such errors with an ErrorBoundary (which can be a subcomponent; doesn't need to be the whole UI). Or you can use a helper like https://github.com/get-convex/convex-helpers/blob/main/packages/convex-helpers/README.md#richer-usequery
GitHub
convex-helpers/packages/convex-helpers/README.md at main · get-conv...
A collection of useful code to complement the official packages. - get-convex/convex-helpers
Thank you so much ðŸ˜