Skip to content

fix: Add loading state only on the correct button on the login screen#2910

Draft
Elouan1411 wants to merge 1 commit into
mainfrom
remove-double-loader-login-screen
Draft

fix: Add loading state only on the correct button on the login screen#2910
Elouan1411 wants to merge 1 commit into
mainfrom
remove-double-loader-login-screen

Conversation

@Elouan1411
Copy link
Copy Markdown
Contributor

No description provided.

Copilot AI review requested due to automatic review settings May 21, 2026 09:17
@Elouan1411 Elouan1411 marked this pull request as draft May 21, 2026 09:19
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adjusts the login screen’s loading-state handling so only the button initiating the action shows a loading indicator.

Changes:

  • Replace the shared startLoadingLoginButtons() call with a login-specific startLoadingLoginButton().
  • Add a separate startLoadingSignUpButton() and trigger it when navigating to account creation.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 207 to 210
private fun openAccountCreation() {
startLoadingSignUpButton()
safelyNavigate(LoginFragmentDirections.actionLoginFragmentToNewAccountFragment())
}
@Elouan1411 Elouan1411 force-pushed the remove-double-loader-login-screen branch from 89e7b17 to 2e6d852 Compare May 21, 2026 11:02
@sonarqubecloud
Copy link
Copy Markdown

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants