Skip to content

fix: go to previous step when connection fails #77

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

Merged
merged 2 commits into from
Apr 10, 2025

Conversation

fioan89
Copy link
Collaborator

@fioan89 fioan89 commented Apr 9, 2025

  • happens when an error is encountered during connection (like exceptions caused by an expired token)
  • right now the auth wizard stays on the last step.
  • with this changeset the auth steps reset to the initial sign in for auto-connect, or it goes back one step back to the token input step for manual authentication

- happens when an error is encountered during connection (like exceptions caused by an expired token)
- right now the auth wizard stays on the last step.
- with this changeset the auth steps reset to the initial sign in for auto-connect, or it goes back one step
  back to the token input step for manual authentication
@fioan89 fioan89 requested review from matifali and bcpeinhardt April 9, 2025 21:38
@matifali
Copy link
Member

Does this mean we go back to the enter deployment URL screen without pressing the back button?

@fioan89
Copy link
Collaborator Author

fioan89 commented Apr 10, 2025

Does this mean we go back to the enter deployment URL screen without pressing the back button?

In the case of "auto-login" yes, it jumps back to the initial deployment url and it also shows an error notification. For the manual login sequence, it goes back only one step - to the token page and similarly it shows a notification error.

@fioan89 fioan89 merged commit e313f45 into main Apr 10, 2025
5 checks passed
@fioan89 fioan89 deleted the fix-go-to-previous-step-when-connection-fails branch April 10, 2025 18:24
@matifali
Copy link
Member

@fioan89, can you ask for reviews from @f0ssel instead of @bcpeinhardt going forward? Thanks.

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