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

maintenance: release 2301 prep - v13.9.0 #2166

Closed
wants to merge 154 commits into from
Closed

Conversation

profnandaa
Copy link
Member

@profnandaa profnandaa commented Jan 31, 2023

13.9.0

New Features / Validators

Fixes and Enhancements

New and Improved Locales

rak810 and others added 30 commits May 27, 2021 10:04
* Fixes #1761 for Bangladesh and Myanmar Mobile Validation and Test

* Updated README.md for the Myanmar Mobile Number

* Updated Test for the Myanmar Mobile Number

* Fixing the Myanmar Prefix

* Reverting the Change on the Mobile Number for BD

* Fixing the Naming Convention and Pattern
* feat(isMACAddress): add EUI-64 validation

* Update src/lib/isMACAddress.js

Co-authored-by: Sarhan Aissi <tux-tn@users.noreply.github.com>

* Add possible values of eui to README.md

Co-authored-by: Rik Smale <WikiRik@users.noreply.github.com>
Co-authored-by: Sarhan Aissi <tux-tn@users.noreply.github.com>
* feat: add support for Swedish license plates

* feat: allow spaces

* fix(docs): sort alphabetically

* fix(isLicensePlate): Trim, disallow 0 and fix regex
* Additional test cases for isPostalCode validator CA, PL, UA

* [The Social Insurance Number (SIN)](https://www.canada.ca/en/employment-social-development/services/sin.html)

* Function docstring corrected

* Canadian SIN is a part of general TaxID validator

* Redundant line of code + test fixed

* Valid ISO 639-1 + ISO 3166-1 alpha 2 locale
.substr() is deprecated so we replace it with .slice() which works similarily but isn't deprecated
Signed-off-by: Tobias Speicher <rootcommander@gmail.com>
Forgot to remove the old regex in my last commit
Copy link
Member

@WikiRik WikiRik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't taken a look at the changed test file (yet), but I do have some remarks on things we should update in the future. But it's not for this release, we should be able to ship it with these commits

dinersclub: /^3(?:0[0-5]|[68][0-9])[0-9]{11}$/,
discover: /^6(?:011|5[0-9][0-9])[0-9]{12,15}$/,
jcb: /^(?:2131|1800|35\d{3})\d{11}$/,
mastercard: /^5[1-5][0-9]{2}|(222[1-9]|22[3-9][0-9]|2[3-6][0-9]{2}|27[01][0-9]|2720)[0-9]{12}$/, // /^[25][1-7][0-9]{14}$/;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why this alternative RegExp is in the comments, but maybe we can look at that in #2117

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it looks like the comment is a more "generalized" version of the final regexp used here.
I would tend to vote to remove the comment, it only causes confusion, but again, this can be part of my refactor #2117

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think removal is the best and also best to do in the refactor

@@ -132,6 +149,9 @@ const phones = {
'zh-CN': /^((\+|00)86)?(1[3-9]|9[28])\d{9}$/,
'zh-TW': /^(\+?886\-?|0)?9\d{8}$/,
'dz-BT': /^(\+?975|0)?(17|16|77|02)\d{6}$/,
'ar-YE': /^(((\+|00)9677|0?7)[0137]\d{7}|((\+|00)967|0)[1-7]\d{6})$/,
'ar-EH': /^(\+?212|0)[\s\-]?(5288|5289)[\s\-]?\d{5}$/,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not just this one, but we should not check for [\s\-] in this validator. But that's part of #2124

'bg-BG': bgBgCheck,
'cs-CZ': csCzCheck,
'de-AT': deAtCheck,
'de-DE': deDeCheck,
'dk-DK': dkDkCheck,
'el-CY': elCyCheck,
'el-GR': elGrCheck,
'en-CA': isCanadianSIN,
Copy link
Member

@WikiRik WikiRik Jan 31, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should have been called enCaCheck but we can fix this in a later refactor, it doesn't affect the user

profnandaa and others added 3 commits January 31, 2023 22:20
clean-up #1932 
---------

Co-authored-by: Mik <37216885+mik7up@users.noreply.github.com>
- fixes #2040
- clean-up #2041 

Co-authored-by: coolbeatz71 <sigmacool@gmail.com>
Co-authored-by: Alvaro Castro <moltar89@gmail.com>

@profnandaa: clean up #2103
@@ -342,6 +342,37 @@ const validators = {
};
return checkIdCardNo(str);
},
'zh-HK': (str) => {
// sanitize user input
str = str.trim();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMHO, this sanitization step does not belong inside the validator, but I guess we can take a look after the release.
related issue #2158

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure.

@@ -11,10 +11,11 @@ const patterns = {
AT: fourDigit,
AU: fourDigit,
AZ: /^AZ\d{4}$/,
BA: /^([7-8]\d{4}$)/,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that [7-8] range is unnecessary, but that is a tiny style issue only.
#2141 will be dealing with a lot of these

@pano9000
Copy link
Contributor

pano9000 commented Feb 1, 2023

@profnandaa
one tiny thing I'd like to add again, please also include: #2160

fix(isEmail): fixed `isFQDN` still checking email length when
 `ignore_max_length` is `true`

profnandaa: clean-up #2128

---------

Co-authored-by: Said Akhmedbayev <said.akh@gmail.com>
Co-authored-by: Said Akhmedbayev <said.akhmedbayev@accenture.com>
profnandaa and others added 4 commits February 2, 2023 06:03
* maintentance: clean up, closes #2073
---------

Co-authored-by: Digambar <digambartu@gmail.com>
* maintenance: clean up #2061

---------

Co-authored-by: djeks922 <djeks922@gmail.com>
Co-authored-by: Frederike Ramin <frederike.ramin@digitalservice.bund.de>
@codecov
Copy link

codecov bot commented Feb 2, 2023

Codecov Report

Base: 100.00% // Head: 100.00% // No change to project coverage 👍

Coverage data is based on head (54d330c) compared to base (47ee5ad).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@               Coverage Diff               @@
##           release_2301     #2166    +/-   ##
===============================================
  Coverage        100.00%   100.00%            
===============================================
  Files               102       105     +3     
  Lines              2059      2324   +265     
  Branches            464       586   +122     
===============================================
+ Hits               2059      2324   +265     
Impacted Files Coverage Δ
src/lib/isMobilePhone.js 100.00% <ø> (ø)
src/lib/isPassportNumber.js 100.00% <ø> (ø)
src/lib/isPostalCode.js 100.00% <ø> (ø)
src/lib/toDate.js 100.00% <ø> (ø)
src/index.js 100.00% <100.00%> (ø)
src/lib/alpha.js 100.00% <100.00%> (ø)
src/lib/isAfter.js 100.00% <100.00%> (ø)
src/lib/isBIC.js 100.00% <100.00%> (ø)
src/lib/isBase32.js 100.00% <100.00%> (ø)
src/lib/isBtcAddress.js 100.00% <100.00%> (ø)
... and 111 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@profnandaa
Copy link
Member Author

@rubiin @pano9000 @WikiRik -- I have now added the release notes on the PR description. Would like a review for typos, etc. We should be good to go, releasing this evening, God willing!

@profnandaa
Copy link
Member Author

#2160

Oh, sure, will include that in a fix commit.

@profnandaa profnandaa changed the title maintenance: release 2301 prep maintenance: release 2301 prep - v13.9.0 Feb 2, 2023
@pano9000
Copy link
Contributor

pano9000 commented Feb 2, 2023

@profnandaa nice work! :-)
Question: is there a reason for this being 13.9.0 and not 13.8.0, when the last version was 13.7.0?

also would be maybe nice if #2107 could be mentioned under "Documentation fixes" as well :-) ;-)

@profnandaa
Copy link
Member Author

profnandaa commented Feb 2, 2023 via email

@profnandaa
Copy link
Member Author

@pano9000 -- my bad, I don't know how I missed #2107 ; was actually confusing with another one coz I was just on email. Adding it.

Co-authored-by: Rik Smale <13023439+WikiRik@users.noreply.github.com>
Co-authored-by: ST-DDT <ST-DDT@gmx.de>

- rename isLuhnValid -> isLuhnNumber
- docs: add th-TH in isAlpha*
@@ -143,7 +143,7 @@ Validator | Description
**isLicensePlate(str, locale)** | check if the string matches the format of a country's license plate.<br/><br/>`locale` is one of `['cs-CZ', 'de-DE', 'de-LI', 'en-IN', 'es-AR', 'hu-HU', 'pt-BR', 'pt-PT', 'sq-AL', 'sv-SE']` or `'any'`.
**isLocale(str)** | check if the string is a locale.
**isLowercase(str)** | check if the string is lowercase.
**isLuhnValid(str)** | check if the string passes the [Luhn check][Luhn Check].
**isLuhnNumber(str)** | check if the string passes the [Luhn algorithm check](https://en.wikipedia.org/wiki/Luhn_algorithm).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**isLuhnNumber(str)** | check if the string passes the [Luhn algorithm check](https://en.wikipedia.org/wiki/Luhn_algorithm).
**isLuhnNumber(str)** | check if the string passes the [Luhn algorithm check][Luhn Check].

Line 300 already makes sure it links to that wikipedia page so this should be fine

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't affect the user so we can fix in a later PR as well

@profnandaa
Copy link
Member Author

We did it, thanks folks! 🎉
npm: https://www.npmjs.com/package/validator/v/13.9.0
github: https://github.com/validatorjs/validator.js/releases/tag/13.9.0

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

Successfully merging this pull request may close these issues.