Skip to content

Conversation

cryptodev-2s
Copy link
Contributor

@cryptodev-2s cryptodev-2s commented Sep 8, 2025

Explanation

This PR migrates ShieldController 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

@cryptodev-2s cryptodev-2s self-assigned this Sep 8, 2025
@cryptodev-2s cryptodev-2s requested review from a team as code owners September 8, 2025 14:13
@cryptodev-2s cryptodev-2s changed the title refactor: migrate ShieldController to @metamask/messenger refactor: migrate ShieldController to @metamask/messenger Sep 8, 2025
@cryptodev-2s cryptodev-2s mentioned this pull request Sep 8, 2025
42 tasks
@@ -47,6 +48,11 @@ export function getDefaultShieldControllerState(): ShieldControllerState {
};
}

export type ShieldControllerGetStateAction = ControllerGetStateAction<
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we add this to index.ts, and then add a changelog entry for this?

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