Fix #1871: Improve initial board setup loading UI with informative text #2065
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title: Feat/Fix: Add informative UI to initial board setup loader (Closes #1871)
Closes #1871
Description of Change
This PR addresses the user experience issue where the application would show a dark screen with a bare spinner during the one-time 'initial board setup' process, causing user confusion.
Solution
I replaced the singular
<CircularProgress />component in the loading condition with an expanded UI block. This new screen includes the spinner along with centered, informative text (e.g., 'Setting up your personalized boards...') to explain the brief wait to the user.Testing/Verification
Note to Maintainers: I have successfully confirmed the local development environment starts and the code compiles without errors. However, I was unable to fully test the Sign Up flow on my local machine due to a server connectivity error (likely needing local backend/DB setup).
I am confident the front-end change is correct and request maintainers to perform the final functional verification on the sign-up flow during the PR review.