This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
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.
Wait for initial profile load before displaying widget #7556
Wait for initial profile load before displaying widget #7556
Changes from 3 commits
5c76682
20d2fa3
4a3e0b7
9cf7aec
97c6002
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a given, the event only fires after a setState which always sets the fetchedAt so this if statement will never fail
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the update event is also emitted on a reset, where state is set to
{}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That happens during logout/soft-logout when everything is unmounted, but if you're keeping this if statement then going back to the
on
listener is better otherwise you would handle areset
case wrong (not that the component would remain rendered for it to matter but better be consistent with your approach I guess)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought I would hit the reset case in the in-room registration flow i'm working on for a customer ticket but yeah, it looks like the
RoomView
+AppTile
are remounted anyway. Will remove this check and stick withonce