feat(isISBN): allow usage of options object by WikiRik · Pull Request #2157 · validatorjs/validator.js

WikiRik · 2023-01-29T22:57:32Z

This PR implements steps 1 and 2 of #1874 for isISBN.

Checklist

PR contains only changes related; no stray files, etc.
README updated (where applicable)
Tests written (where applicable)

codecov · 2023-01-29T22:58:45Z

Codecov Report

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

Coverage data is based on head (845148d) compared to base (753c29d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@ Coverage Diff @@## master #2157 +/- ##
=========================================
Coverage 100.00% 100.00% =========================================
Files 105 105 Lines 2334 2334 Branches 586 586 =========================================
Hits 2334 2334

Impacted Files	Coverage Δ
src/lib/isISBN.js	`100.00% <100.00%> (ø)`

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

LGTM

profnandaa · 2023-01-30T07:44:49Z

+ });
+ });
+
+ describe('(legacy syntax)', () => {


Thanks for the backward compatibilty! 👍

profnandaa · 2023-01-30T07:45:45Z

One more review, we can get this in too, in this coming release. /cc. @pano9000

pano9000 · 2023-01-30T08:20:52Z

 }
- const sanitized = str.replace(/[\s-]+/g, '');
+
+ const sanitizedIsbn = isbn.replace(/[\s-]+/g, '');


a bit off topic for the PR;
I would like to see that "sanitization" step replaced with as option, maybe something like a "strict" mode, checking/ignoring for spaces or hyphens only inside the ISBN, not also at the beginning or end of the ISBN string.
but that shouldn't be part of this PR, just noting it down for the future

Yes, I had that in mind as well when working on this but from personal experience people write the ISBN down differently. I haven't checked if there are rules on where the - should be, but I think that in this case sanitising whitespaces and - adds value to this specific validator.
About the beginning/end of the string; that's not something I thought of but if you want I can add that

no, don't worry about it here, IMHO that would be out of scope for this particular PR - let's keep it simple and get this merged and then after the release, we can work on that via a new PR, I'd say

pano9000

looks good to me, other than that double exclamation mark remark, which is maybe a bit on the nitpicking side :-)

pano9000

thank you, looks good to me

profnandaa · 2023-01-30T17:54:18Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

WikiRik · 2023-01-30T17:55:46Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

That's only happening when something that has write access does the review, and I don't think they have that

pano9000 · 2023-01-30T19:11:31Z

@profnandaa @WikiRik is correct, I only am a "mod member" currently (which is totally fine for now), so my review do not "fully" count

WikiRik · 2023-01-29T22:57:32Z

This PR implements steps 1 and 2 of #1874 for isISBN.

Checklist

PR contains only changes related; no stray files, etc.
README updated (where applicable)
Tests written (where applicable)

codecov · 2023-01-29T22:58:45Z

Codecov Report

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

Coverage data is based on head (845148d) compared to base (753c29d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@ Coverage Diff @@## master #2157 +/- ##
=========================================
Coverage 100.00% 100.00% =========================================
Files 105 105 Lines 2334 2334 Branches 586 586 =========================================
Hits 2334 2334

Impacted Files	Coverage Δ
src/lib/isISBN.js	`100.00% <100.00%> (ø)`

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

LGTM

profnandaa · 2023-01-30T07:44:49Z

+ });
+ });
+
+ describe('(legacy syntax)', () => {


Thanks for the backward compatibilty! 👍

profnandaa · 2023-01-30T07:45:45Z

One more review, we can get this in too, in this coming release. /cc. @pano9000

pano9000 · 2023-01-30T08:20:52Z

 }
- const sanitized = str.replace(/[\s-]+/g, '');
+
+ const sanitizedIsbn = isbn.replace(/[\s-]+/g, '');


a bit off topic for the PR;
I would like to see that "sanitization" step replaced with as option, maybe something like a "strict" mode, checking/ignoring for spaces or hyphens only inside the ISBN, not also at the beginning or end of the ISBN string.
but that shouldn't be part of this PR, just noting it down for the future

Yes, I had that in mind as well when working on this but from personal experience people write the ISBN down differently. I haven't checked if there are rules on where the - should be, but I think that in this case sanitising whitespaces and - adds value to this specific validator.
About the beginning/end of the string; that's not something I thought of but if you want I can add that

no, don't worry about it here, IMHO that would be out of scope for this particular PR - let's keep it simple and get this merged and then after the release, we can work on that via a new PR, I'd say

pano9000

looks good to me, other than that double exclamation mark remark, which is maybe a bit on the nitpicking side :-)

pano9000

thank you, looks good to me

profnandaa · 2023-01-30T17:54:18Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

WikiRik · 2023-01-30T17:55:46Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

That's only happening when something that has write access does the review, and I don't think they have that

pano9000 · 2023-01-30T19:11:31Z

@profnandaa @WikiRik is correct, I only am a "mod member" currently (which is totally fine for now), so my review do not "fully" count

WikiRik · 2023-01-29T22:57:32Z

This PR implements steps 1 and 2 of #1874 for isISBN.

Checklist

PR contains only changes related; no stray files, etc.
README updated (where applicable)
Tests written (where applicable)

codecov · 2023-01-29T22:58:45Z

Codecov Report

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

Coverage data is based on head (845148d) compared to base (753c29d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@ Coverage Diff @@## master #2157 +/- ##
=========================================
Coverage 100.00% 100.00% =========================================
Files 105 105 Lines 2334 2334 Branches 586 586 =========================================
Hits 2334 2334

Impacted Files	Coverage Δ
src/lib/isISBN.js	`100.00% <100.00%> (ø)`

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

LGTM

profnandaa · 2023-01-30T07:44:49Z

+ });
+ });
+
+ describe('(legacy syntax)', () => {


Thanks for the backward compatibilty! 👍

profnandaa · 2023-01-30T07:45:45Z

One more review, we can get this in too, in this coming release. /cc. @pano9000

pano9000 · 2023-01-30T08:20:52Z

 }
- const sanitized = str.replace(/[\s-]+/g, '');
+
+ const sanitizedIsbn = isbn.replace(/[\s-]+/g, '');


a bit off topic for the PR;
I would like to see that "sanitization" step replaced with as option, maybe something like a "strict" mode, checking/ignoring for spaces or hyphens only inside the ISBN, not also at the beginning or end of the ISBN string.
but that shouldn't be part of this PR, just noting it down for the future

Yes, I had that in mind as well when working on this but from personal experience people write the ISBN down differently. I haven't checked if there are rules on where the - should be, but I think that in this case sanitising whitespaces and - adds value to this specific validator.
About the beginning/end of the string; that's not something I thought of but if you want I can add that

no, don't worry about it here, IMHO that would be out of scope for this particular PR - let's keep it simple and get this merged and then after the release, we can work on that via a new PR, I'd say

pano9000

looks good to me, other than that double exclamation mark remark, which is maybe a bit on the nitpicking side :-)

pano9000

thank you, looks good to me

profnandaa · 2023-01-30T17:54:18Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

WikiRik · 2023-01-30T17:55:46Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

That's only happening when something that has write access does the review, and I don't think they have that

pano9000 · 2023-01-30T19:11:31Z

@profnandaa @WikiRik is correct, I only am a "mod member" currently (which is totally fine for now), so my review do not "fully" count

WikiRik · 2023-01-29T22:57:32Z

This PR implements steps 1 and 2 of #1874 for isISBN.

Checklist

PR contains only changes related; no stray files, etc.
README updated (where applicable)
Tests written (where applicable)

codecov · 2023-01-29T22:58:45Z

Codecov Report

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

Coverage data is based on head (845148d) compared to base (753c29d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@ Coverage Diff @@## master #2157 +/- ##
=========================================
Coverage 100.00% 100.00% =========================================
Files 105 105 Lines 2334 2334 Branches 586 586 =========================================
Hits 2334 2334

Impacted Files	Coverage Δ
src/lib/isISBN.js	`100.00% <100.00%> (ø)`

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

LGTM

profnandaa · 2023-01-30T07:44:49Z

+ });
+ });
+
+ describe('(legacy syntax)', () => {


Thanks for the backward compatibilty! 👍

profnandaa · 2023-01-30T07:45:45Z

One more review, we can get this in too, in this coming release. /cc. @pano9000

pano9000 · 2023-01-30T08:20:52Z

 }
- const sanitized = str.replace(/[\s-]+/g, '');
+
+ const sanitizedIsbn = isbn.replace(/[\s-]+/g, '');


a bit off topic for the PR;
I would like to see that "sanitization" step replaced with as option, maybe something like a "strict" mode, checking/ignoring for spaces or hyphens only inside the ISBN, not also at the beginning or end of the ISBN string.
but that shouldn't be part of this PR, just noting it down for the future

Yes, I had that in mind as well when working on this but from personal experience people write the ISBN down differently. I haven't checked if there are rules on where the - should be, but I think that in this case sanitising whitespaces and - adds value to this specific validator.
About the beginning/end of the string; that's not something I thought of but if you want I can add that

no, don't worry about it here, IMHO that would be out of scope for this particular PR - let's keep it simple and get this merged and then after the release, we can work on that via a new PR, I'd say

pano9000

looks good to me, other than that double exclamation mark remark, which is maybe a bit on the nitpicking side :-)

pano9000

thank you, looks good to me

profnandaa · 2023-01-30T17:54:18Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

WikiRik · 2023-01-30T17:55:46Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

That's only happening when something that has write access does the review, and I don't think they have that

pano9000 · 2023-01-30T19:11:31Z

@profnandaa @WikiRik is correct, I only am a "mod member" currently (which is totally fine for now), so my review do not "fully" count

WikiRik · 2023-01-29T22:57:32Z

This PR implements steps 1 and 2 of #1874 for isISBN.

Checklist

PR contains only changes related; no stray files, etc.
README updated (where applicable)
Tests written (where applicable)

codecov · 2023-01-29T22:58:45Z

Codecov Report

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

Coverage data is based on head (845148d) compared to base (753c29d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@ Coverage Diff @@## master #2157 +/- ##
=========================================
Coverage 100.00% 100.00% =========================================
Files 105 105 Lines 2334 2334 Branches 586 586 =========================================
Hits 2334 2334

Impacted Files	Coverage Δ
src/lib/isISBN.js	`100.00% <100.00%> (ø)`

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

LGTM

profnandaa · 2023-01-30T07:44:49Z

+ });
+ });
+
+ describe('(legacy syntax)', () => {


Thanks for the backward compatibilty! 👍

profnandaa · 2023-01-30T07:45:45Z

One more review, we can get this in too, in this coming release. /cc. @pano9000

pano9000 · 2023-01-30T08:20:52Z

 }
- const sanitized = str.replace(/[\s-]+/g, '');
+
+ const sanitizedIsbn = isbn.replace(/[\s-]+/g, '');


a bit off topic for the PR;
I would like to see that "sanitization" step replaced with as option, maybe something like a "strict" mode, checking/ignoring for spaces or hyphens only inside the ISBN, not also at the beginning or end of the ISBN string.
but that shouldn't be part of this PR, just noting it down for the future

Yes, I had that in mind as well when working on this but from personal experience people write the ISBN down differently. I haven't checked if there are rules on where the - should be, but I think that in this case sanitising whitespaces and - adds value to this specific validator.
About the beginning/end of the string; that's not something I thought of but if you want I can add that

no, don't worry about it here, IMHO that would be out of scope for this particular PR - let's keep it simple and get this merged and then after the release, we can work on that via a new PR, I'd say

pano9000

looks good to me, other than that double exclamation mark remark, which is maybe a bit on the nitpicking side :-)

pano9000

thank you, looks good to me

profnandaa · 2023-01-30T17:54:18Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

WikiRik · 2023-01-30T17:55:46Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

That's only happening when something that has write access does the review, and I don't think they have that

pano9000 · 2023-01-30T19:11:31Z

@profnandaa @WikiRik is correct, I only am a "mod member" currently (which is totally fine for now), so my review do not "fully" count

WikiRik · 2023-01-29T22:57:32Z

This PR implements steps 1 and 2 of #1874 for isISBN.

Checklist

PR contains only changes related; no stray files, etc.
README updated (where applicable)
Tests written (where applicable)

codecov · 2023-01-29T22:58:45Z

Codecov Report

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

Coverage data is based on head (845148d) compared to base (753c29d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@ Coverage Diff @@## master #2157 +/- ##
=========================================
Coverage 100.00% 100.00% =========================================
Files 105 105 Lines 2334 2334 Branches 586 586 =========================================
Hits 2334 2334

Impacted Files	Coverage Δ
src/lib/isISBN.js	`100.00% <100.00%> (ø)`

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

LGTM

profnandaa · 2023-01-30T07:44:49Z

+ });
+ });
+
+ describe('(legacy syntax)', () => {


Thanks for the backward compatibilty! 👍

profnandaa · 2023-01-30T07:45:45Z

One more review, we can get this in too, in this coming release. /cc. @pano9000

pano9000 · 2023-01-30T08:20:52Z

 }
- const sanitized = str.replace(/[\s-]+/g, '');
+
+ const sanitizedIsbn = isbn.replace(/[\s-]+/g, '');


a bit off topic for the PR;
I would like to see that "sanitization" step replaced with as option, maybe something like a "strict" mode, checking/ignoring for spaces or hyphens only inside the ISBN, not also at the beginning or end of the ISBN string.
but that shouldn't be part of this PR, just noting it down for the future

Yes, I had that in mind as well when working on this but from personal experience people write the ISBN down differently. I haven't checked if there are rules on where the - should be, but I think that in this case sanitising whitespaces and - adds value to this specific validator.
About the beginning/end of the string; that's not something I thought of but if you want I can add that

no, don't worry about it here, IMHO that would be out of scope for this particular PR - let's keep it simple and get this merged and then after the release, we can work on that via a new PR, I'd say

pano9000

looks good to me, other than that double exclamation mark remark, which is maybe a bit on the nitpicking side :-)

pano9000

thank you, looks good to me

profnandaa · 2023-01-30T17:54:18Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

WikiRik · 2023-01-30T17:55:46Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

That's only happening when something that has write access does the review, and I don't think they have that

pano9000 · 2023-01-30T19:11:31Z

@profnandaa @WikiRik is correct, I only am a "mod member" currently (which is totally fine for now), so my review do not "fully" count

WikiRik · 2023-01-29T22:57:32Z

This PR implements steps 1 and 2 of #1874 for isISBN.

Checklist

PR contains only changes related; no stray files, etc.
README updated (where applicable)
Tests written (where applicable)

codecov · 2023-01-29T22:58:45Z

Codecov Report

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

Coverage data is based on head (845148d) compared to base (753c29d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@ Coverage Diff @@## master #2157 +/- ##
=========================================
Coverage 100.00% 100.00% =========================================
Files 105 105 Lines 2334 2334 Branches 586 586 =========================================
Hits 2334 2334

Impacted Files	Coverage Δ
src/lib/isISBN.js	`100.00% <100.00%> (ø)`

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

LGTM

profnandaa · 2023-01-30T07:44:49Z

+ });
+ });
+
+ describe('(legacy syntax)', () => {


Thanks for the backward compatibilty! 👍

profnandaa · 2023-01-30T07:45:45Z

One more review, we can get this in too, in this coming release. /cc. @pano9000

pano9000 · 2023-01-30T08:20:52Z

 }
- const sanitized = str.replace(/[\s-]+/g, '');
+
+ const sanitizedIsbn = isbn.replace(/[\s-]+/g, '');


a bit off topic for the PR;
I would like to see that "sanitization" step replaced with as option, maybe something like a "strict" mode, checking/ignoring for spaces or hyphens only inside the ISBN, not also at the beginning or end of the ISBN string.
but that shouldn't be part of this PR, just noting it down for the future

Yes, I had that in mind as well when working on this but from personal experience people write the ISBN down differently. I haven't checked if there are rules on where the - should be, but I think that in this case sanitising whitespaces and - adds value to this specific validator.
About the beginning/end of the string; that's not something I thought of but if you want I can add that

no, don't worry about it here, IMHO that would be out of scope for this particular PR - let's keep it simple and get this merged and then after the release, we can work on that via a new PR, I'd say

pano9000

looks good to me, other than that double exclamation mark remark, which is maybe a bit on the nitpicking side :-)

pano9000

thank you, looks good to me

profnandaa · 2023-01-30T17:54:18Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

WikiRik · 2023-01-30T17:55:46Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

That's only happening when something that has write access does the review, and I don't think they have that

pano9000 · 2023-01-30T19:11:31Z

@profnandaa @WikiRik is correct, I only am a "mod member" currently (which is totally fine for now), so my review do not "fully" count

WikiRik · 2023-01-29T22:57:32Z

This PR implements steps 1 and 2 of #1874 for isISBN.

Checklist

PR contains only changes related; no stray files, etc.
README updated (where applicable)
Tests written (where applicable)

codecov · 2023-01-29T22:58:45Z

Codecov Report

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

Coverage data is based on head (845148d) compared to base (753c29d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@ Coverage Diff @@## master #2157 +/- ##
=========================================
Coverage 100.00% 100.00% =========================================
Files 105 105 Lines 2334 2334 Branches 586 586 =========================================
Hits 2334 2334

Impacted Files	Coverage Δ
src/lib/isISBN.js	`100.00% <100.00%> (ø)`

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

LGTM

profnandaa · 2023-01-30T07:44:49Z

+ });
+ });
+
+ describe('(legacy syntax)', () => {


Thanks for the backward compatibilty! 👍

profnandaa · 2023-01-30T07:45:45Z

One more review, we can get this in too, in this coming release. /cc. @pano9000

pano9000 · 2023-01-30T08:20:52Z

 }
- const sanitized = str.replace(/[\s-]+/g, '');
+
+ const sanitizedIsbn = isbn.replace(/[\s-]+/g, '');


a bit off topic for the PR;
I would like to see that "sanitization" step replaced with as option, maybe something like a "strict" mode, checking/ignoring for spaces or hyphens only inside the ISBN, not also at the beginning or end of the ISBN string.
but that shouldn't be part of this PR, just noting it down for the future

Yes, I had that in mind as well when working on this but from personal experience people write the ISBN down differently. I haven't checked if there are rules on where the - should be, but I think that in this case sanitising whitespaces and - adds value to this specific validator.
About the beginning/end of the string; that's not something I thought of but if you want I can add that

no, don't worry about it here, IMHO that would be out of scope for this particular PR - let's keep it simple and get this merged and then after the release, we can work on that via a new PR, I'd say

pano9000

looks good to me, other than that double exclamation mark remark, which is maybe a bit on the nitpicking side :-)

pano9000

thank you, looks good to me

profnandaa · 2023-01-30T17:54:18Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

WikiRik · 2023-01-30T17:55:46Z

@pano9000 -- wondering why your review is not being counted as a member's review 🤔 (still showing grey tick).

That's only happening when something that has write access does the review, and I don't think they have that

pano9000 · 2023-01-30T19:11:31Z

@profnandaa @WikiRik is correct, I only am a "mod member" currently (which is totally fine for now), so my review do not "fully" count

feat(isISBN): allow usage of options object
cef15ac

WikiRik mentioned this pull request Jan 29, 2023
[Refactor proposal] Move optional parameters to options object #1874
Open

profnandaa previously approved these changes Jan 30, 2023
View reviewed changes

profnandaa added the needs-more-review label Jan 30, 2023

pano9000 reviewed Jan 30, 2023
View reviewed changes

Comment threadsrc/lib/isISBN.js Outdated

style: remove double exclamation mark
845148d

WikiRik dismissed profnandaa’s stale review via 845148dJanuary 30, 2023 10:59

WikiRik mentioned this pull request Jan 30, 2023
Idea: Unifying sanitizing in validators #2158
Open

pano9000 approved these changes Jan 30, 2023
View reviewed changes

profnandaa approved these changes Jan 30, 2023
View reviewed changes

profnandaa merged commit 6dba289 into validatorjs:masterJan 30, 2023

profnandaa mentioned this pull request Feb 2, 2023
maintenance: release 2301 prep - v13.9.0 #2166
Closed

Santhosh-Kumar-99 mentioned this pull request Feb 15, 2023
[feat]GSTIN Number Validation and PAN Validation (Multiple TIN functionality) and also refactored is taxID for options object #2153
Closed
3 tasks

rntvicente mentioned this pull request May 24, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.11.0 rntvicente/ts-clean-architecture#25
Open

sahilpawar58 mentioned this pull request May 25, 2024
[Snyk] Upgrade validator from 13.6.0 to 13.11.0 sahilpawar58/Civil-Project#47
Open

ChinmoyHembram mentioned this pull request May 25, 2024
[Snyk] Upgrade validator from 13.7.0 to 13.11.0 ChinmoyHembram/Cocktail-recipel-site#260
Open

wambugucoder mentioned this pull request May 30, 2024
[Snyk] Upgrade validator from 13.5.1 to 13.12.0 wambugucoder/MERN-STACK-APP-FCC-CHALLENGE#628
Open

rntvicente mentioned this pull request May 30, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 rntvicente/ts-clean-architecture#27
Open

DefenderK mentioned this pull request May 30, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#68
Closed

ChinmoyHembram mentioned this pull request May 30, 2024
[Snyk] Upgrade validator from 13.7.0 to 13.12.0 ChinmoyHembram/Cocktail-recipel-site#263
Open

ceconcarlsen mentioned this pull request May 31, 2024
[Snyk] Upgrade validator from 13.7.0 to 13.12.0 ceconcarlsen/mern-app#6
Open

sumandas0 mentioned this pull request May 31, 2024
[Snyk] Upgrade validator from 13.0.0 to 13.12.0 sumandas0/Cassandra_node#30
Open

This was referenced Jun 3, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#70
Closed
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#73
Closed

IT21275210 mentioned this pull request Jun 8, 2024
[Snyk] Upgrade validator from 13.7.0 to 13.12.0 IT21275210/Health_record_management_System#3
Open

snyk-ioBot mentioned this pull request Jun 10, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#76
Closed

florinMiro mentioned this pull request Jun 11, 2024
[Snyk-dev] Upgrade validator from 13.5.2 to 13.12.0 florinMiro/nodejs-goof-renamed#56
Closed

snyk-ioBot mentioned this pull request Jun 11, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#79
Closed

This was referenced Jun 12, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#80
Closed
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#84
Closed

snyk-ioBot mentioned this pull request Jun 13, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#85
Closed

DefenderK mentioned this pull request Jun 13, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#86
Closed

This was referenced Jun 14, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#87
Closed
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#91
Closed

DefenderK mentioned this pull request Jun 14, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#92
Closed

This was referenced Jun 20, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#95
Closed
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#97
Closed

snyk-ioBot mentioned this pull request Jun 28, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#101
Closed

This was referenced Jul 10, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#105
Closed
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#109
Closed
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#112
Closed

rm-neilsondesa mentioned this pull request Jul 16, 2024
[Snyk] Upgrade validator from 13.7.0 to 13.12.0 rm-neilsondesa/EH-Patch-Todo-App#26
Open

snyk-ioBot mentioned this pull request Jul 18, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#114
Closed

DefenderK mentioned this pull request Jul 18, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#116
Closed

This was referenced Jul 19, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#119
Closed
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#121
Closed
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#123
Closed

luizhp mentioned this pull request Aug 21, 2024
[Snyk] Upgrade validator from 13.0.0 to 13.12.0 luizhp/template-api-tdd#8
Open

This was referenced Aug 30, 2024
[Snyk] Upgrade validator from 13.7.0 to 13.12.0 TheJ-Erk400/passbolt_browser_extension#11
Open
[Snyk] Upgrade validator from 13.7.0 to 13.12.0 TheJ-Erk400/passbolt_cli2#4
Open

sumandas0 mentioned this pull request Sep 8, 2024
[Snyk] Upgrade: lodash, cassandra-driver, validator sumandas0/Cassandra_node#32
Open

TheJ-Erk400 mentioned this pull request Sep 8, 2024
[Snyk] Upgrade: jssha, validator TheJ-Erk400/passbolt_cli2#6
Open

KOTTAGENVH mentioned this pull request Sep 27, 2024
[Snyk] Upgrade validator from 13.7.0 to 13.12.0 anjana-madushan/E-COMMERCE-WEB-APP-ITP-PROJ-#11
Open

DefenderK mentioned this pull request Oct 30, 2024
[Snyk] Upgrade validator from 13.5.2 to 13.12.0 DefenderK/nodejs-goof#132
Closed