-
Notifications
You must be signed in to change notification settings - Fork 626
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
Backups V2 Follow-up Fixes / Improvements #6213
base: develop
Are you sure you want to change the base?
Conversation
…nbow into @matthew/APP-1297
… is not storing proper data, and create new backup every time the user wants to backup
<Portal /> | ||
<PortalConsumer /> |
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.
These are now no longer re-rendering the entire app when re-rendering
</Portal> | ||
<Portal /> | ||
<PortalConsumer /> | ||
<BackupsSync /> |
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.
In charge of initial backup store sync on mount
const AppWithRedux = connect<AppProps, AppDispatch, AppProps, AppState>( | ||
state => ({ | ||
walletReady: state.appState.walletReady, | ||
}), | ||
null, | ||
null, | ||
{ | ||
areStatesEqual: (next, prev) => { | ||
// Only update if walletReady actually changed | ||
return next.appState.walletReady === prev.appState.walletReady; | ||
}, | ||
areOwnPropsEqual: shallowEqual, | ||
} | ||
)(memo(App)); |
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.
we only really want to re-render the App when walletReady has changed.. this fixes that
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 logic was moved into backupStore
Fixes APP-1297
What changed (plus any additional context for devs)
Currently there is multiple places this hook is used, so my hunch is the useState variable
password
was being wiped between uses and causing issues.Screen recordings / screenshots
What to test