Description

Removes a recently introduced base-controller patch that assigns the default argument string to the AllowedAction and AllowedEvent generic parameters of the class RestrictedControllerMessenger.

This patch was created in 81e2d18 as part of an intended fix for the breaking changes introduced by @metamask/base-controller v4.0.0. The fix was accomplished by a later commit d3a1dc7 (#8607), but the now-redundant patch was never removed.

This patch is too dangerous to keep as is, because it negates the allowlist security we have in place for our controller-messengers. This potentially enables any messenger to access any external action or event without restrictions.

The CI run shows that removing this patch does not break anything. This is because it's not actually affecting the code in any way (for now).

TL;DR The patch is not only safe to remove -- it's unsafe not to remove.

Related issues

• Fixes issue introduced here feat: bump mobile snaps packages to bring new snaps architecture #8607
• Patch was introduced as an intended fix for [base-controller] getRestricted infers the wrong types when it has no allowed actions/events core#3648. However, this issue is only relevant to the ControllerMessenger.getRestrictedMessenger method, and not to the RestrictedControllerMessenger class that is altered in the patch.

Manual testing steps

Screenshots/Recordings

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.