-
-
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
fix: add wildcard for custody keyring #3899
Conversation
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
Do you think instead of this method keyrings should have a default account name and provide a get method to expose it? That way we wouldn't need to worry about this mapping and we can make it part of the API |
Its a good idea, lets plan this out when we refactor the keyrings to use the keyring api |
## Explanation This pr resolves the special case when passing a custody keyring type to the function keyringTypeToName. ## References Fixes: MetaMask/accounts-planning#233 ## Changelog ### `@metamask/keyring-controller` - **CHANGED**: Custody keyring type. ## Checklist - [x] I've updated the test suite for new or updated code as appropriate - [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [ ] I've highlighted breaking changes using the "BREAKING" category above as appropriate --------- Co-authored-by: Gustavo Antunes <[email protected]>
Explanation
This pr resolves the special case when passing a custody keyring type to the function keyringTypeToName.
References
Fixes: https://github.com/MetaMask/accounts-planning/issues/233
Changelog
@metamask/keyring-controller
Checklist