-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
Sync stale vault on keyring store update #1384
Merged
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
mikesposito
force-pushed
the
fix/stale-vault
branch
from
May 23, 2023 09:50
ab236e0
to
e469d67
Compare
gantunesr
reviewed
May 23, 2023
mikesposito
changed the title
Update stale vault during
Sync stale vault on keyring store update
May 23, 2023
fullUpdate
gantunesr
previously approved these changes
May 23, 2023
mikesposito
force-pushed
the
fix/stale-vault
branch
from
May 24, 2023 09:14
a951c92
to
7970f4a
Compare
Gudahtt
approved these changes
May 24, 2023
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.
LGTM!
brad-decker
pushed a commit
to dragana8/core
that referenced
this pull request
Jun 1, 2023
* fix: update vault during fullUpdate * refactor: use event handler instead of fullUpdate * docs: rollback fullUpdate description
MajorLift
pushed a commit
that referenced
this pull request
Oct 11, 2023
* fix: update vault during fullUpdate * refactor: use event handler instead of fullUpdate * docs: rollback fullUpdate description
MajorLift
pushed a commit
that referenced
this pull request
Oct 11, 2023
* fix: update vault during fullUpdate * refactor: use event handler instead of fullUpdate * docs: rollback fullUpdate description
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.
Description
Currently,
KeyringController
has avault
in state that is never updated after its construction, which doesn't make sense and poses the risk of clients using this stale value.This "outer"
vault
should be always in sync with the "inner"vault
managed by@metamask/eth-keyring-controller
(this.#keyring
inKeyringController
).This PR adds an
EthKeyringController
store subscription in theKeyringController
constructor, syncing the vaults on each update.Changes
KeyringController
andEthKeyingController
vaults are now kept in syncReferences
Checklist