-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
fix: Ticket Order: User able to add invalid email #5690
fix: Ticket Order: User able to add invalid email #5690
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/eventyay/open-event-frontend/6ayhzhylc |
Codecov Report
@@ Coverage Diff @@
## development #5690 +/- ##
===============================================
+ Coverage 23.77% 23.78% +0.01%
===============================================
Files 509 509
Lines 5414 5415 +1
Branches 59 59
===============================================
+ Hits 1287 1288 +1
+ Misses 4112 4111 -1
- Partials 15 16 +1
Continue to review full report at Codecov.
|
@iamareebjamal Please see the change I have made. And also I have one more suggestion, there are other places as well besides this where email validation is failing, so should I fix them also?? |
Failing for valid email |
is it so? |
@iamareebjamal pls validate and see if its working now? |
@iamareebjamal ofcourse we can't validate every possible case b for that validating through OTP would be best but for now this sol looks good to me then before where invalid emails where not validated |
Exactly. It's better to allow invalid emails than not allow valid emails |
So should I do now anything for it? bcz acc to @mariobehling in the issue OTP feature will be done later and he was asking to validate whether .com is there so what I'm thing is to use simple regExp that validates this which which take care of .com as well as not ignore valid emails bcz now foreg. 'tz@g' is valid which is for sure we can take care by using simple regExp. @iamareebjamal Whats say? |
The regex should not filter out any valid email |
I think current validation is ok because adding any regex for validating accurate email address will surely filter out valid ones. Because the validation of email is also a part of the provider. some emails are valid but not acceptable by one provider while acceptable by another provider. Even RFC can't validate 100% emails. |
https://ihateregex.io/expr/email/ Simple enough and does not filter out most of valid emails. |
OK
? like in loginForm etc |
This pull request introduces 1 alert when merging 6ce3701 into 9314043 - view on LGTM.com new alerts:
|
No, just here |
ok I'll do it here only |
This pull request introduces 1 alert when merging 0d225ea into 9314043 - view on LGTM.com new alerts:
|
@iamareebjamal I have done the changes, and eslint error error is coming. |
yarn lint |
how to fix this yarn lint error? |
yarn lint |
either we have to disable no-control-regex |
This pull request introduces 1 alert when merging c9c20ad into c874482 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging ade6c83 into c874482 - view on LGTM.com new alerts:
|
Fixes #5277
Short description of what this resolves:
Email are only added if they are valid
Changes proposed in this pull request:
Checklist
development
branch.