Replies: 1 comment 1 reply
-
This breaking change should have bumped us to 0.15.0 as per the conventions of SemVer version 0, so that was a mistake in versioning, but still not the most egregious fault since version 0 of SemVer is generally considered unstable. Let's move to #1775 for a discussion of the overall project progression and goals. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I updated to v0.14.2 just the other day, which added the default option
forbidUnknownValues: true
(totally agree!), see: #2196But this library is here for ages already and this was really a breaking change on the major version "0" 😉.
So my suggestion is, bump to a new major, and be done with it, lets go to 1.0 right?
5 votes ·
Beta Was this translation helpful? Give feedback.
All reactions