More detailed logging on function not found
Since convex doesn’t support versioning, mobile users might get outdated query and mutations names, so if at least we could get auth data or userAgents or something.
2 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!
I think the current frontend+backend fused development methodology makes it easier to break things. But historically in the apps I've worked in we've had a very strict policy of not breaking endpoints. There are various things people use including protobuffers to help enforce this.
If using pure built in Convex stuff, I'd make sure all my public convex funcitons have returns and args validators. That essentially defines your protocol/contract you're not allowed to break. Then you ensure that you don't willy-nilly change the validators. You only make non-breaking changes like: marking things as optional, not-removing fields etc.
If you truly get to a point where you don't want to keep adding to the same function, you can always create a new function for newer apps.
It is useful to know what version of the client is calling. So I would probably use customFunctions and custom query hooks on the react side to add / validate extra metadata about the calling client.
Customizing serverless functions without middleware
Re-use code and centralize request handler definitions with discoverability and type safety and without the indirection of middleware or nesting of wr...