Indy
CCConvex Community
•Created by AlphaOmega on 3/24/2025 in #support-community
More detailed logging on function not found
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.
3 replies
CCConvex Community
•Created by OK on 3/3/2025 in #support-community
How to connect flutter and Convex
cc @Mohan Singh who built that flutter package
10 replies
CCConvex Community
•Created by IDIR on 9/27/2023 in #support-community
Flutter and Convex ?
We'll likely not look back into this area for a little while unfortunately. Thanks for pointing it out
35 replies