-
Notifications
You must be signed in to change notification settings - Fork 80
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
[Onboarding] Refactor LoginScreen to make store independent and part of the OnboardingFlow #17160
Comments
micieslak
added a commit
that referenced
this issue
Jan 29, 2025
- LoginScreen SB page simplified - OnboardingLayoutPage - settings introduced for handier testing - LoginScreen moved from OnboardingLayout to OnboardingFlow, making first flow's page bound to model content (instead of relying on check during initialization) - UnblockWithPukFlow removed from OnboardingLayout (now it's used only in OnboardingFlow) - Login error/success processing extracted from LoginScreen to OnboardingLayout - small bug fixed in Utils::objectTypeName Closes: #17160
1 task
micieslak
added a commit
that referenced
this issue
Jan 30, 2025
- LoginScreen SB page simplified - OnboardingLayoutPage - settings introduced for handier testing - LoginScreen moved from OnboardingLayout to OnboardingFlow, making first flow's page bound to model content (instead of relying on check during initialization) - UnblockWithPukFlow removed from OnboardingLayout (now it's used only in OnboardingFlow) - Login error/success processing extracted from LoginScreen to OnboardingLayout - small bug fixed in Utils::objectTypeName Closes: #17160
micieslak
added a commit
that referenced
this issue
Jan 30, 2025
- LoginScreen SB page simplified - OnboardingLayoutPage - settings introduced for handier testing - LoginScreen moved from OnboardingLayout to OnboardingFlow, making first flow's page bound to model content (instead of relying on check during initialization) - UnblockWithPukFlow removed from OnboardingLayout (now it's used only in OnboardingFlow) - Login error/success processing extracted from LoginScreen to OnboardingLayout - small bug fixed in Utils::objectTypeName Closes: #17160
micieslak
added a commit
that referenced
this issue
Jan 30, 2025
- LoginScreen SB page simplified - OnboardingLayoutPage - settings introduced for handier testing - LoginScreen moved from OnboardingLayout to OnboardingFlow, making first flow's page bound to model content (instead of relying on check during initialization) - UnblockWithPukFlow removed from OnboardingLayout (now it's used only in OnboardingFlow) - Login error/success processing extracted from LoginScreen to OnboardingLayout - small bug fixed in Utils::objectTypeName Closes: #17160
micieslak
added a commit
that referenced
this issue
Jan 31, 2025
- LoginScreen SB page simplified - OnboardingLayoutPage - settings introduced for handier testing - LoginScreen moved from OnboardingLayout to OnboardingFlow, making first flow's page bound to model content (instead of relying on check during initialization) - UnblockWithPukFlow removed from OnboardingLayout (now it's used only in OnboardingFlow) - Login error/success processing extracted from LoginScreen to OnboardingLayout - small bug fixed in Utils::objectTypeName Closes: #17160
github-project-automation
bot
moved this from Code Review
to Done
in Status Desktop/Mobile Board
Jan 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The idea is to make the
LoginScreen
simpler, without ui-unrelated logc and wiring with the store done the layer above,OnboardingLayout
.The text was updated successfully, but these errors were encountered: