Function "versions" / Behavior across deployments
First off - really loving Convex! The DX is astounding, and I love that it allows me to "not think about" things, however to trust Convex really handles those things well, I need to have a high-level understanding of how it all works. The docs surrounding caching, consistency, idempotent mutations, deterministic queries all give me comfort that I can just ignore transactions essentially, and "trust the reactor" - thank you for the wonderful docs there and also James's talk on Software Engineering Daily really helped.
One thing that wasn't clear to me from the docs, was how functions work across deploys. For example, if I have deploy a version of my software with a query Q1, and then deploy another version where Q1 is either renamed, removed, or edited. What happens when frontend clients (with a cached version of the page for example) call Q1? Does convex do anything special here? Or do I just need to treat the filepath + exported function name as the "stable identifier" of a function - and treat it with the same respect and backwards compatibility requirements that I would a normal API endpoint?
One thing that wasn't clear to me from the docs, was how functions work across deploys. For example, if I have deploy a version of my software with a query Q1, and then deploy another version where Q1 is either renamed, removed, or edited. What happens when frontend clients (with a cached version of the page for example) call Q1? Does convex do anything special here? Or do I just need to treat the filepath + exported function name as the "stable identifier" of a function - and treat it with the same respect and backwards compatibility requirements that I would a normal API endpoint?
