Skip to content
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

Merged
merged 8 commits into from
Feb 15, 2024

Conversation

montelaidev
Copy link
Contributor

@montelaidev montelaidev commented Feb 7, 2024

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

  • CHANGED: Custody keyring type.

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • 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

@montelaidev montelaidev requested a review from a team as a code owner February 7, 2024 09:40
Copy link
Member

@gantunesr gantunesr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@gantunesr
Copy link
Member

gantunesr commented Feb 9, 2024

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

@montelaidev
Copy link
Contributor Author

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

@montelaidev montelaidev merged commit 67a602d into main Feb 15, 2024
136 checks passed
@montelaidev montelaidev deleted the fix/ap233/custody-wildcard-check branch February 15, 2024 17:43
MajorLift pushed a commit that referenced this pull request Feb 16, 2024
## 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]>
@MajorLift MajorLift mentioned this pull request Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants