-
Notifications
You must be signed in to change notification settings - Fork 363
fix: improve Safe loading error handling #3728
Conversation
CLA Assistant Lite All Contributors have signed the CLA. |
ESLint Summary View Full Report
[warning] react-hooks/exhaustive-deps
Report generated by eslint-plus-action |
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.
Really clean to move the onboard related logic into one place 👍
It works, if the safe doesn't load it retries after a few seconds and it loads fine then I have issues with the store of the "viwed safes". The safe, after failing and then loading properly is not saved in that storage. |
Awsome. cool fix. Looks good to me |
What it solves
Safe loading error screen persisting
How this PR fixes it
If the Safe fails to load, but then succeeds on the next scheduled poll, the "Safe couldn't be loaded" error screen is removed. The Safe is only removed from viewed Safes if the user clicks on the error page button.
This is a duplicate of #3717, based off #3727 instead as it includes associated fixes.
How to test it
Open a Safe on a throttled connection and observe the error message appear. When the loading has succeeded, it should now dissapear and not remove it from the viewed Safes cache.