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
We have users onboarding that input their emails in lowercase, despite the email being returned from GitHub being CamelCase. Most users assume case-insensitivity in emails, which causes the friction here.
Being able to cast the email to lowercase will allow for a lot less friction in our onboarding processes.
Proposed Solution
I propose to sdd the code that @VF-mbrauer implemented originally in the Microsoft connector to the GitHub connector.
I'd also suggest that the flag be added to the other connectors as well, as I assume that other people might experience similar issues.
Alternatives Considered
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
I was actually wondering why so much of it was repeated across the different connectors. Makes a lot of sense!
I can absolutely see the benefit of a generic middleware layer, but it seems like there's been some difficulty in moving it forward in an incremental way without PRs trying to cover every use-case.
In that case I would still appreciate if the flag for just the GitHub connector could be reviewed in the interim.
Additionally, I'll take a stab at adding a Dex Enhacement Proposal for the above issue, as I'd really love to see that moving forward.
Preflight Checklist
Problem Description
Follows in the vein of #1725
We have users onboarding that input their emails in lowercase, despite the email being returned from GitHub being CamelCase. Most users assume case-insensitivity in emails, which causes the friction here.
Being able to cast the email to lowercase will allow for a lot less friction in our onboarding processes.
Proposed Solution
I propose to sdd the code that @VF-mbrauer implemented originally in the Microsoft connector to the GitHub connector.
I'd also suggest that the flag be added to the other connectors as well, as I assume that other people might experience similar issues.
Alternatives Considered
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: