-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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(auth): adjust button variant based on sign-in-up step #9188
Conversation
Update the button variant to dynamically switch between 'secondary' and 'primary' based on the current step in the sign-in-up flow. Ensures the UI reflects the correct state, improving user experience and consistency.
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.
PR Summary
This PR modifies the MainButton component's visual state in the authentication flow to provide better user feedback by dynamically adjusting the button variant based on the current sign-in/sign-up step.
- Updates
SignInUpGlobalScopeForm.tsx
to set button variant to 'secondary' for initial step and 'primary' for password step - Button text changes from 'Continue' to 'Sign Up' when transitioning to password step
- Maintains visual consistency with existing Google/Microsoft auth buttons in the same form
1 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile
signInUpStep === SignInUpStep.Password ? 'Sign Up' : 'Continue' | ||
} |
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.
logic: Button shows 'Sign Up' in Password step but SignInUpMode could be SignIn - this may confuse users
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.
Perfect!
Thanks @AMoreaux for your contribution! |
Update the button variant to dynamically switch between 'secondary' and 'primary' based on the current step in the sign-in-up flow. Ensures the UI reflects the correct state, improving user experience and consistency.