Fixfrontendbug#71#1238
Closed
aditisingh70330 wants to merge 7 commits intoGreedyBear-Project:mainfrom
Closed
Conversation
aditisingh70330
force-pushed
the
fixfrontendbug#71
branch
from
484e7a0 to
a7576b5
Compare
Member
|
Hey @aditisingh70330 ! There are a lot of problems with this PR. For example it targets the wrong branch (that's why I will have to close it). Please go through the contribution guidelines again. |
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
2 participants
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.
I investigated the reported AppHeader rendering behavior by observing component renders during navigation and authentication state changes. The behavior appears consistent with expected React patterns, where re-renders are triggered by state and route updates.
I also reviewed the loading flow and verified the FallbackLoading component from @certego/certego-ui. It correctly handles suspended routes and provides a consistent UI fallback during lazy loading, ensuring smooth transitions while async components are resolved.
Additionally, I observed 502 Bad Gateway responses from /api/auth/authentication and /api/news, indicating that the backend/API service is not reachable in the current setup, which limits full end-to-end validation of the flow.
From the frontend perspective, the AppHeader rendering logic and loading behavior appear stable based on current observable behavior.