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|Date where they really should use JsonNumber and ValidDate etc (even though this has been discussed\raised multiple times). Number and Date could be renamed to include Unsafe (or Js or Native), and a codemod could be created to help with transition. I bet many people would find themselves realising that they chose the wrong schema for the job, in which case they could choose to opt into the safer type by not applying the codemod (staying with now safe Number, instead of converting to UnsafeNumber)?
