`schemaValidation: false` for some parts of the schema
Hi, we love having schemaValidation turned on for most of our tables and parts of our documents.
However, we have several documents that have different properties based on a
A helpful example might be to think about how Notion lets you convert between blocks that have different properties, but if you go from
However, we have several documents that have different properties based on a
type field, and ideally we'd still like to have nice type inference during development, without being strictly limited to storing foreign properties in a document.A helpful example might be to think about how Notion lets you convert between blocks that have different properties, but if you go from
todo to heading and back to todo it still remembers the properties of the original todo block. Does that make sense?
