- Notifications
You must be signed in to change notification settings - Fork4
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
fioan89 commentedApr 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
matifali commentedApr 10, 2025
Does this mean we go back to the enter deployment URL screen without pressing the back button? |
fioan89 commentedApr 10, 2025
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. |
e313f45 intomainUh oh!
There was an error while loading.Please reload this page.
matifali commentedApr 10, 2025
@fioan89, can you ask for reviews from@f0ssel instead of@bcpeinhardt going forward? Thanks. |