Consider renaming built-in types to emphasize safety in v4
Would you consider, for v4, moving away from the approach which mirrors TS semantics for built in types like Number and Date, which leads to invalid date, NaN etc being allowed by the "default" schemas?
In my team we find that people keep reaching for
In my team we find that people keep reaching for
Schema.Number|DateJsonNumberValidDateUnsafeJsNativeNumberUnsafeNumber
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
