feat: Migrate controller guidelines and examples to new Messenger #6335
Conversation
This file contains hidden or 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
Gudahtt
force-pushed
the
messenger-migrate-controller-docs
branch
2 times, most recently
from
815bf50 to
39756ca
Compare
Gudahtt
force-pushed
the
messenger-migrate-base-controller
branch
2 times, most recently
from
ae71891 to
67c7853
Compare
Gudahtt
force-pushed
the
messenger-migrate-controller-docs
branch
4 times, most recently
from
0a1a16b to
0bdc3d1
Compare
Gudahtt
force-pushed
the
messenger-migrate-controller-docs
branch
from
0bdc3d1 to
7bbe29c
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Gudahtt
added a commit
that referenced
this pull request
Aug 20, 2025
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.
4 tasks
Gudahtt
added a commit
that referenced
this pull request
Aug 20, 2025
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.
This comment was marked as resolved.
This comment was marked as resolved.
Gudahtt
added a commit
that referenced
this pull request
Aug 20, 2025
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.
Gudahtt
added a commit
that referenced
this pull request
Aug 21, 2025
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.
Gudahtt
added a commit
that referenced
this pull request
Aug 21, 2025
…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
Gudahtt
force-pushed
the
messenger-migrate-controller-docs
branch
2 times, most recently
from
c4836ce to
d669a35
Compare
Member
Author
|
Rebased to resolve conflict (the messenger package publish) |
43 tasks
mcmire
reviewed
Aug 21, 2025
Contributor
mcmire
left a comment
mcmire
left a comment
There was a problem hiding this comment.
Had some minor comments, but overall these changes make sense.
packages/sample-controllers/src/sample-gas-prices-controller.test.ts
Outdated
Show resolved
Hide resolved
4 tasks
mcmire
reviewed
Aug 22, 2025
Gudahtt
force-pushed
the
messenger-migrate-controller-docs
branch
2 times, most recently
from
0f4215d to
5d451a9
Compare
Gudahtt
force-pushed
the
messenger-migrate-controller-docs
branch
from
efa167b to
80d7730
Compare
|
No dependency changes detected. Learn more about Socket for GitHub. 👍 No dependency changes detected in pull request |
Member
|
nit: we should run |
cryptodev-2s
approved these changes
Oct 27, 2025
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.
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.