refactor: migrate RemoteFeatureFlagController
to @metamask/messenger
#6502
+64
−57
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
This PR migrates
RemoteFeatureFlagController
to the new@metamask/messenger
message bus, as opposed to the one exported from@metamask/base-controller
.References
Checklist
Note
Migrates
RemoteFeatureFlagController
to@metamask/messenger
, updates metadata and tests, adjusts exports/types, and adds the new dependency.RestrictedMessenger
in@metamask/base-controller
toMessenger
from@metamask/messenger
.@metamask/base-controller/next
and metadata keys (anonymous
->includeInDebugSnapshot
).controllerName
internal; updates tests to define and use namespaced messenger instances.RemoteFeatureFlagControllerState
type toremote-feature-flag-controller
and export it from there; remove it fromremote-feature-flag-controller-types
.index.ts
exports accordingly.deriveStateFromMetadata
usage and snapshots.@metamask/messenger
dependency and TS project references.Messenger
.Written by Cursor Bugbot for commit a0fdd49. This will update automatically on new commits. Configure here.