Update express-validator to version 3.2.0 🚀 #68
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
Codecov Report
@@ Coverage Diff @@
## master #68 +/- ##
=======================================
Coverage 34.13% 34.13%
=======================================
Files 7 7
Lines 416 416
Branches 70 70
=======================================
Hits 142 142
Misses 274 274Continue to review full report at Codecov.
|
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.
Hello lovely humans,
express-validator just published its new version 3.2.0.
This version 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 express-validator.
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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
The new version differs by 123 commits .
153de323.2.095ae3c4Merge pull request #337 from ChaseMoskal/testableea2c2abImprove testability and class scopingf85819dAdd test suite for general testabilityb983e4f3.1.30bdadadMerge pull request #329 from jyotman/markdown-fix194faeffix markdown title syntax in README.md841944eMerge pull request #310 from kacepe/patch-1a6f689dAllow to use fully custom error formatter.6652e04Merge branch 'eslint'3c997fdRemove JSHint and JSCS stuffeaced95npm: switch JSCS and JSHint scripts with ESLint34eb328eslint: add initial config and fix offending code59099b8Travis: use only LTS + current Node.js versions8e8f635Merge pull request #304 from akifo/masterThere are 123 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.