Skip to content

Conversation

cryptodev-2s
Copy link
Contributor

Explanation

This PR migrates NetworkEnablementController to the new @metamask/messenger message bus, as opposed to the one exported from @metamask/base-controller.

References

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 communicated my changes to consumers by updating changelogs for packages I've changed, highlighting breaking changes as necessary
  • I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

cursor[bot]

This comment was marked as outdated.

@cryptodev-2s cryptodev-2s force-pushed the cryptodev-2s/messenger/network-enablement-controller branch 2 times, most recently from 294d507 to 9130d1e Compare September 10, 2025 11:13
cursor[bot]

This comment was marked as outdated.

@cryptodev-2s cryptodev-2s force-pushed the cryptodev-2s/messenger/network-enablement-controller branch from 9130d1e to 44f2265 Compare September 10, 2025 11:28
}
throw new Error(`Unexpected action type: ${actionType}`);
});
const mockGetNetworkState = jest.fn().mockImplementation(() => ({
Copy link
Contributor

Choose a reason for hiding this comment

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

I know we ought to migrate these tests so we aren't mocking the messenger, but could we leave these changes to another PR or do we have to do it here?

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.

2 participants