-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update joi to the latest version 馃殌 #33
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Version 10.3.1 just got published.Update to this version instead 馃殌 CommitsThe new version differs by 7 commits .
See the full diff. |
Version 10.3.2 just got published. |
Version 10.3.3 just got published. |
Version 10.3.4 just got published. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 10.3.0 of joi just got published.
The version 10.3.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of joi.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 20 commits .
5d484b7
10.3.0
33d45d1
Avoid unnecessary clones
bad211a
Switch to using hapitoc
6f4377b
Strip keys after a full validation of the objects
374f52e
Local object().unknown() should override stripUnknown option
2765e90
Upgrade lab
49a0c76
Allow extensions factory functions
3b34640
Keep extensions from inheriting root properties
37b8dc6
Merge pull request #1112 from AaronHarris/patch-1
434df05
Merge pull request #1115 from dwelle/master
90d488a
Added clarifying docs around
optional
behavior (fixes #1111).90da318
(docs) Improve README with clarification on callbacks (#636)
d09e342
Merge pull request #1107 from DavidTPate/issue-1098
1188d00
Added docs around
convert
flag functionality for each of the types. Fixes #10989e44c96
Fix #1105
There are 20 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 馃尨