-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
♻️ refactor: Login and Registration component Improvement #2716
♻️ refactor: Login and Registration component Improvement #2716
Conversation
* display error message when API is down * add loading animation to Login form while fetching data * optimize startupConfig to fetch data only on initial render to prevent unnecessary API calls
Awesome, looks great. Thank you for consolidating the logic, too. I'll be testing this soon. |
@ohneda can you make me a contributor? I made some changes so we can optimize this a bit further. If you add me, I can avoid closing this PR and pushing to your branch. Also could use your help on aligning request/reset password pages with the changes I made, which will make sense once you see them |
@danny-avila Thanks, I have added you as a contributor to my repository. |
Was hoping to get to this today along with a few other PRs but ran out of time. Will try to be back on it Sunday/Monday |
Thanks for letting me know. All my PR are not urgent, so no need to rush |
@ohneda my changes are all wrapped up, can you confirm it's all working as intended on your end? |
@danny-avila Thanks, Everything is working as intended and it's become more clear! I see that the request/reset password pages have been updated too. Is there anything else I need to work on? |
Thanks for checking! |
Summary
I've made some improvements to the
Login
andRegistration
components.Login
andRegistration
displayed a blank screen while fetchingStartupConfig
data from the API. I've added a blinking logo that appears while the forms wait for the API to return theStartupConfig
data. No worries, if you don't like this effect, you can simply remove the BlinkAnimation wrapper.1.mov
Login
component only to make one API call for StartupConfig, even if the component re-renders after a failed login attempt.I initially planned to make just a small improvement, but it turned into a bit of a larger change. However, the functionality of the
Login
andRegistration
components remains the same.Please let me know if you have any concerns. I hope these changes can help improve the user experience, even if just a little bit.
Change Type
Checklist