Challenges with Defining Type Guard for Allowed Schemas
Hi all! I'm trying to build an abstraction on top of
To mean: "valid field schemas are any schema that can encode to string" (and don't need any context)
But because of how the variance for
The variance setup makes sense to prevent incompatible schemas being used interchangably, but it makes it hard (impossible?) to "talk about" types of schemas before they are used.
Any advice? Thanks a lot!
@effect/schemaTo mean: "valid field schemas are any schema that can encode to string" (and don't need any context)
But because of how the variance for
IAThe variance setup makes sense to prevent incompatible schemas being used interchangably, but it makes it hard (impossible?) to "talk about" types of schemas before they are used.
Any advice? Thanks a lot!
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
