Uh oh!
There was an error while loading. Please reload this page.
feat: Migrate controller guidelines and examples to new Messenger - #6335
Conversation
815bf50 to
39756caCompareae71891 to
67c7853Compare0a1a16b to
0bdc3d1Compare0bdc3d1 to
7bbe29cCompare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as resolved.
This comment was marked as resolved.
Tests that used the `@metamask/base-controller/next` export were not working correctly until after a build was completed. They were using the built code rather than the source code. On CI the tests run without any build, so they would always fail. This was resolved up updating the TSConfig and Jest config to map the `next` export to the correct source code. This unblocks #6335 as well as other controller migrations to the upcoming BaseController version.
…6349) ## Explanation Tests that used the `@metamask/base-controller/next` export were not working correctly until after a build was completed. They were using the built code rather than the source code. On CI the tests run without any build, so they would always fail. This was resolved up updating the TSConfig and Jest config to map the `next` export to the correct source code. This unblocks #6335 as well as other controller migrations to the upcoming BaseController version. ## References Relates to #5626 ## 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 - [x] I've communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs), highlighting breaking changes as necessary - [x] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes
c4836ce to
d669a35CompareGudahtt
commented
Aug 21, 2025
Rebased to resolve conflict (the messenger package publish) |
mcmire
left a comment
There was a problem hiding this comment.
Had some minor comments, but overall these changes make sense.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
0f4215d to
5d451a9Compareefa167b to
80d7730CompareNo dependency changes detected. Learn more about Socket for GitHub. 👍 No dependency changes detected in pull request |
mikesposito
commented
Oct 23, 2025
nit: we should run |
Explanation
Migrate the controller guidelines and the
sample-controllerspackage to thenextexport of the@metamask/base-controllerpackage and the newMessengerclass from@metamask/messenger.References
Relates to #5626
Checklist
Note
Migrate controller docs and sample-controllers to the new @metamask/messenger Messenger and @metamask/base-controller/next, updating APIs, metadata, tests, and dependencies.
@metamask/messengerMessengerinstead ofRestrictedMessenger; update examples for actions/events typing, root/child messenger setup, delegation, and selector utilities (MessengerActions/MessengerEvents).messenger.call/subscribe/publish/registerMethodActionHandlers.@metamask/sample-controllers)@metamask/base-controller/nextand@metamask/messenger.messagingSystem.*withmessenger.*; update controller/service messenger types toMessenger<...>and constructor usage.anonymous→includeInDebugSnapshot).Messenger, mock namespace utilities, andMessengerActions/MessengerEvents.@metamask/messenger; update TS project references.sample_controllers --> messenger; add middleware/controller edge; list@metamask/messengerpackage.Written by Cursor Bugbot for commit c1ad7a4. This will update automatically on new commits. Configure here.