Feedback: schemaValidation and strictTableNameTypes documentation is difficult to comprehend
The docs for schemaValidation and strictTableNameTypes https://docs.convex.dev/database/schemas is primarily written in prose. A chart may help. I'm trying to understand the impact of my settings for these two properties
Rhetorical questions:
1) Which tables are validated during runtime?
2) Which tables get Intellisense in VS Code?
3) What are the implications for deploying table definition changes?
4) What changes if a table is in defineSchema() or not? It seems like I have two ways to control behavior: Include tables in defineSchema() or change these settings. So what do I do if I want Intellisense, but I don't want strict validation during runtime, but I also don't want to compromise my entire schema by setting schemaValidation=false?
Rhetorical questions:
1) Which tables are validated during runtime?
2) Which tables get Intellisense in VS Code?
3) What are the implications for deploying table definition changes?
4) What changes if a table is in defineSchema() or not? It seems like I have two ways to control behavior: Include tables in defineSchema() or change these settings. So what do I do if I want Intellisense, but I don't want strict validation during runtime, but I also don't want to compromise my entire schema by setting schemaValidation=false?
Schema validation keeps your Convex data neat and tidy. It also gives you end-to-end TypeScript type safety!
Join the Convex Discord! Explore Convex, the backend platform that keeps your app in sync.
15,010Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
