You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's no easy way to ensure the Ecto field/column is case insensitive, while not limiting the underlying database. And I wonder if making the normalization function configurable is the right approach. Why do you want it to maintain the case?
I have some users in my application who type their emails using uppercase letters. They complained about seeing their emails modified within the app.
More importantly though, from RFC 5321, section 2.3.11, the part before the "@" could be case-sensitive, since it is entirely under the control of the host system. This basically means that in rare cases, email delivery will fail for emails that needed to have upper case letters, and in my app I do send emails
When I register with an email with upper case letters, they are converted to lowercase.
This is happening here
I want to maintain the upper case letters. Is there a simple way to allow for this?
The text was updated successfully, but these errors were encountered: