Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency express-validator to v5 #5

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 5, 2018

This PR contains the following updates:

Package Type Update Change References
express-validator dependencies major ^3.1.2 -> ^5.0.0 homepage, source

Release Notes

express-validator/express-validator

v5.3.1

Compare Source

  • #​673 - check: add missing ; that would cause TypeScript to throw syntax errors

v5.3.0

Compare Source

  • #​579 - docs: major overhaul, and a new home!
    See https://express-validator.github.io for them, with version selection available ✨
  • #​473, #​570 - check: add checkNull and checkFalsy options to exists validator
  • #​568, #​577 - filter: allow including optionals when using matchedData()
  • #​584 - check: don't call sanitizers twice
  • #​593 - check: don't fail when custom validator returns nothing
  • #​598 - check: persist empty validations as the request location itself
  • Upgrade validator to v10.4.0

v5.2.0

Compare Source

express-validator has hit 3k stars 🌟 🌟 🌟 and is its own org 🏢 on GitHub!
  • #​458, #​531, #​563 - check: fix wildcard field selection not validating every array entry
  • #​564 - check: allow exists validator to have message set in schemas
  • #​565 - check: persist values sanitized within oneOf()
  • Update validator to v10.1.0

v5.1.2

Compare Source

  • #​431, #​561 - Make toDate sanitizer and isISO8601 validators work well together
  • #​554, #​560 - filter: don't double sanitize data when using matchedData()

v5.1.1

Compare Source

v5.1.0

Compare Source

New features ✨
  • #​520 - check: whole body validation, like body().isUppercase()
  • #​524 - check: add new standard validations like .isArray() and .isString()
  • check: implement validator negation when using schemas
Bug fixes 🐛
  • #​542 - check: support sanitizers in checkSchema() TypeScript
  • #​548 - check: report errors using original, unsanitized value
  • #​548 - check: don't override validator messages from non-validators in schemas

v5.0.3

Compare Source

  • Don't set undefined values into request when validated key does not exist

v5.0.2

Compare Source

  • #​521 - typescript: add standard sanitizers back to legacy's sanization chain interface

v5.0.1

Compare Source

v5.0.0

Compare Source

No more new features will be added to the legacy API! Only bug fixes will be accepted.

BREAKING CHANGES 💥
  • #​461 - check: sanitizers now persist the sanitized value back to the request. This was previously only the case for sanitizers used from the filter API
  • #​463 - check: standard validators will now use an array's first item only
  • @types/express dependency removed; if you're using express, you must install this yourself now
New features ✨
  • #​433, #​511, #​512 - check: bring schema support back with new checkSchema() function
  • #​445, #​481, #​516 - check, filter: add support for custom sanitizers via .customSanitizer() chain function
  • #​466, #​469, #​489, #​498 - check: accept dynamic message creator function in .withMessage()
  • #​474 - check: add validationResult.withDefaults() which can create a validationResult function with default options set
  • check, filter: build custom check/sanitize functions with buildCheckFunction or buildSanitizeFunction, respectively
Other changes 🐛
  • #​444 - check: make custom validators that resolve a promise succeed without needing to return a truthy value
  • #​458, #​492 - check: partially fix wildcard issues with inexistent fields
  • #​414, #​484 - docs: further describe when and how to use wildcards
  • #​462 - docs: add .formatWith() example
  • #​483 - docs: fix locations accepted in matchedData()
  • #​482 - filter: make oneOf() and matchedData() work together
  • #​496 - Revamp TypeScript support in the library
  • Update validator to v9.4.0

v4.3.0

Compare Source

  • #​434, #​446 - check: accept subgroups of validations
  • #​447, #​453 - filter: list locations to get data from when using matchedData()
  • #​441 - Add nullable option to .optional()

v4.2.1

Compare Source

  • #​425 - Don't sanitize non-string values

v4.2.0

Compare Source

  • #​299 - legacy: use pretty message when validator used in schema doesn't exist
  • #​401 - typescript: set withMessage() arg type to any
  • #​406 - docs: fix req.asyncValidationErrors() return value description
  • #​410 - docs: don't show .throw() without try..catch
  • #​411 - check: make validationResult work even though no validators ran
  • check: add sanitization chain methods
  • filter: add standalone sanitization middleware
  • Remove deprecation warnings from legacy APIs
  • Update validator to v8.2.0

v4.1.1

Compare Source

  • #​398, #​403 - don't fail when .withMessage() is called without any validator
  • #​399 - check: convert value to string just like in v3 (undefined, null, NaN, [] => '')
  • #​400 - check: use any rejection cause as error message
  • #​401 - legacy: restore support for non-string error messages

v4.1.0

Compare Source

  • #​392, #​393 - Add .formatWith(formatter) to the validation result API
  • #​390 - Add .exists() to the TypeScript typings

v4.0.0

Compare Source

🎉 BIGGEST express-validator rewrite ever! 🎉 🎊

...but with backwards compatibility, because we're cool to our users 😉

Most notable features are the introduction of check and filter APIs.
They are additions to express-validator, previous ways to validate your requests are still here, but under the name "legacy APIs".

Check the README for complete docs and the upgrade guide for version 3 users.


Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot. View repository job log here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant