If I want to validate the data users can put in the database I have to use functions. Is there a better way to do data validation then initiating ZOD in every single function and adding a schema for every function individually? I also believe that this could waste a lot of resources.
Hey 👋 For simpler maintenance, I would have 1 function with multiple endpoints. This makes your function's code larger, but with use of some framework, it should be very readable when split across multiple files.
If next iteration of functions goes well (performance-focused), I will pitch idea of .before and .after events. Before events would run syncoronously, and could allow/deny the action - for example document creation. For now, best approach is to execute function from client, and create document inside function
What do you mean by „multiple endpoints“?
This would be insane! Love the idea 🤩
Recommended threads
- Timed out waiting for runtime error
execution id 6a3e0791978712d81ee0 im having issue with appwrite function runtime performance. even after 4gbram and cpu same function sometimes completes in a...
- Function crash first run after a while
Big issue I’m facing , almost all functions crash or run for a very long time the first time i run them after a long time without running them I have a “help-c...
- Function global variables
when i create a top-level global variable in go or bun how will it behave? is the heap getting renewed on every execution or could i do some kind of temp. cachi...