Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
BIT-1003: Generate plus addressed emails #129
BIT-1003: Generate plus addressed emails #129
Changes from all commits
fd28238
0441168
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
๐ค What do you think of moving this to?
ios/BitwardenShared/UI/Platform/Application/Extensions/String.swift
Line 27 in f33f129
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.
Are you proposing replacing this entire guard with the
isValidEmail
check? I think these do slightly different, yet similar things. But if we're trying to match the Xamarin app which has been driving our requirements, theisValidEmail
only checks that the string contains an @ symbol and doesn't check that it isn't the first or last character.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.
Alright, for matching purposes we can leave it like this and refactor in the future. Cause IMO wherever
isValidEmail
is used, when checking if it has a@
it shouldn't be neither the start nor the end of the string so if we'd replace the currentisValidEmail
logic it'd be an improvement. However you're right and let's leave it like this so it's equal to the Xamarin app.