You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
@metamask/remote-feature-flag-controller 6.0.0
Added
BREAKING: Add required getCanonicalProfileId constructor option to RemoteFeatureFlagController for threshold flag segmentation (#9325)
By default, canonical profile ID is used, but MetaMetrics ID can be used when the flag name is present in metaMetricsFlags, typically for scenarios when canonical profile ID is unavailable.
Add optional metaMetricsFlags constructor option to RemoteFeatureFlagController to segment flags by MetaMetrics ID (#9325)
Flags with names present in metaMetricsFlags are segmented by MetaMetrics ID; all others segment by canonical profile ID.
Add optional defaultFeatureFlags constructor option to RemoteFeatureFlagController for client-side defaults as the lowest-precedence layer under processed remote flags and local overrides (#9747)
This must be called during initialization to ensure remoteFeatureFlags is properly recomputed.
BREAKING: Stop redacting IDs from rawRemoteFeatureFlags (#9816)
Existing rawRemoteFeatureFlags properties should be deleted in a migration, so they do not get used for recomputing flags (which would not work properly with a redacted input).
Fixed
Restore remote flag value when overrides are removed/cleared (#9816)
Previously the underlying remote value would be removed as well.
@metamask/wallet 12.0.1
Changed
Bump @metamask/remote-feature-flag-controller from ^5.0.0 to ^6.0.0 (#9945)