Backups V2 Follow-up Fixes / Improvements #6213
Merged
Conversation
This file contains 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
walmat
changed the title
walmat
commented
Nov 8, 2024
…nbow into @matthew/APP-1297
… is not storing proper data, and create new backup every time the user wants to backup
walmat
commented
Nov 18, 2024
walmat
commented
Nov 18, 2024
| </Portal> | ||
| <Portal /> | ||
| <PortalConsumer /> | ||
| <BackupsSync /> |
There was a problem hiding this comment.
In charge of initial backup store sync on mount
walmat
commented
Nov 18, 2024
Comment on lines
+92
to
+105
| 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.
we only really want to re-render the App when walletReady has changed.. this fixes that
walmat
commented
Nov 18, 2024
walmat
commented
Nov 18, 2024
walmat
commented
Nov 18, 2024
Comment on lines
+130
to
+132
| if (!backupProvider) { | ||
| backupsStore.getState().setBackupProvider(WalletBackupTypes.manual); | ||
| } |
There was a problem hiding this comment.
coming from undefined -> manual if not already set to cloud
|
Blocked by #6276 due to multiple AbsolutePortal components being mounted. Merge greg's PR in first so I can rebase and refactor this to use that. |
walmat
removed
the
blocked
derHowie
approved these changes
Dec 19, 2024
brunobar79
reviewed
Dec 19, 2024
| @@ -135,6 +135,7 @@ export function useConsolidatedTransactions( | |||
| keepPreviousData: true, | |||
| getNextPageParam: lastPage => lastPage?.nextPage, | |||
| refetchInterval: CONSOLIDATED_TRANSACTIONS_INTERVAL, | |||
| enabled: !!address, | |||
Comment on lines
+31
to
+33
| const { status } = backupsStore(state => ({ | ||
| status: state.status, | ||
| })); |
There was a problem hiding this comment.
Suggested change
| const { status } = backupsStore(state => ({ | |
| status: state.status, | |
| })); | |
| const status = backupsStore(state => state.status); |
Comment on lines
+56
to
+60
| const { status, backups, mostRecentBackup } = backupsStore(state => ({ | ||
| status: state.status, | ||
| backups: state.backups, | ||
| mostRecentBackup: state.mostRecentBackup, | ||
| })); |
There was a problem hiding this comment.
Suggested change
| const { status, backups, mostRecentBackup } = backupsStore(state => ({ | |
| status: state.status, | |
| backups: state.backups, | |
| mostRecentBackup: state.mostRecentBackup, | |
| })); | |
| const { status, backups, mostRecentBackup } = backupsStore() |
| setIncorrectPassword(false); | ||
| }, []); | ||
|
|
||
| const onSubmit = useCallback(async () => { | ||
| setLoading(true); | ||
| // NOTE: Localizing password to prevent an empty string from being saved if we re-render |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes APP-1297
Fixes APP-1050
Fixes APP-2002
Fixes APP-1649
Fixes APP-2120
What changed (plus any additional context for devs)
This PR introduces a lot of stability changes to backups. I'll layout the important changes here.
UserData.jsonsince it quickly becomes muddy dealing with backup data and user data.backupsStoreZustand store which controls the synced backup dataScreen recordings / screenshots
What to test
https://www.notion.so/rainbowdotme/Backups-V2-Fixes-QA-Hand-off-149b001b85b4800fbf72c0f347b992b0?showMoveTo=true&saveParent=true