-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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(Collaboration): Allow to enforce strict email format on sharees API #45425
Conversation
@AndyScherzinger this would fix the email share issue |
1070d96
to
0c0e296
Compare
Should we add an UI toggle? |
Don't think that is needed. A config value is just fine. This is nothing that gets changed, you chose one or the other (forever) I suppose. |
Only recommend a email address as sharee if it satisfies the strict format checking. Meaning before `a@b` was valid, while now with strict checking it is invalid and needs to be at least `a@b.c` Co-authored-by: Ferdinand Thiessen <opensource@fthiessen.de> Co-authored-by: Benjamin Gaussorgues <benjamin.gaussorgues@nextcloud.com> Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
136bfef
to
a08575c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A bit weird that the config switch only applies to shareapi and not more globally to email validation.
@come-nc should I change this? I would be fine with that. Would be even more clean :) |
See: #45570 |
Closed in favor of #45570 |
Summary
Only recommend a email address as sharee if it satisfies the strict format checking. Meaning before
a@b
was valid, while now with strict checking it is invalid and needs to be at leasta@b.c
Screenshots
Checklist