v10.0.0-1

10.0.0-1

v10.0.0-0

So far, this major version bump exists purely because of a minor (but breaking) change to rttc.parseHuman()-- and specifically only when a primitive type schema is provided. Now, if coercion of the human-entered string fails, a validation error is thrown (whereas before, the base value was used). In other words, parseHuman() is now using rttc.validate() (RTTC loose validation) instead of rttc.coerce() (RTTC coercion).

v9.3.4

rttc@9.3.4 contains assertions to protect against edge cases which can arise when key names contain . when using certain functions, as well as an improved rttc.isEqual() that does not result in false positives

v9.2.0

9.2.0