Skip to content
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

feat: add legacy sign-in #2035

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: add legacy sign-in #2035

wants to merge 1 commit into from

Conversation

whitmanschorn
Copy link
Collaborator

@whitmanschorn whitmanschorn commented Sep 21, 2020

Screen Shot 2020-09-20 at 11 12 12 PM

⚠️
WIP change to allow users to use Auth0 dedicated login page, which includes username/password login.

✅ i18n with locale passed from streetmix
✅ password reset
✅ new account creation
🛑 No design approval. Once we have finalized design, we will update the snapshot for the relevant test.

@whitmanschorn whitmanschorn changed the title feat: add legacy sign-in button feat: add legacy sign-in Sep 21, 2020
@louh
Copy link
Member

louh commented Sep 21, 2020

@whitmanschorn Please format your branch name in the proper convention. See here: https://streetmix.readthedocs.io/en/latest/contributing/code/#submitting-a-pull-request

It is username/feature-name. This is intended to convey project owner. "Feat" doesn't tell us anything. Also, the correct delimiter is dashes, not underscores.

@@ -77,6 +77,14 @@ export function goGoogleSignIn () {
})
}

export function goPasswordSignIn () {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The call to goPasswordSignIn includes a locale parameter, but this does not receive it or do anything with it.

return <button onClick={handleClick}>Auth0 Sign-In</button>
}

export default SignInButton
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, this component is never used anywhere. Why is it included?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like it's meant to generate the button used here. I'm going to commit a change that makes this actually happen.

@easherma
Copy link
Collaborator

@louh is this related to:
#2023

curious where it exists in priority, seems like it could be useful (esp if we are hoping for for monetization from people working at urban planning or academic institutions)

@louh
Copy link
Member

louh commented Nov 20, 2020

@easherma Yes, this is related to that issue. I'd have preferred that the sign in process be part of the Streetmix UI and not a separate page, but even if we were to keep it on a separate page we'd have to do a design review on the look and feel.

This is actually of extremely high importance because there are entire categories of people who are blocked from signing in right now. Enabling email + password login will alleviate some of the problem but we still don't know why passwordless emails are blocked right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants