Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate AlertController to BaseController v2 #25915

Closed
1 of 9 tasks
mcmire opened this issue Jul 17, 2024 · 0 comments · Fixed by #28054
Closed
1 of 9 tasks

Migrate AlertController to BaseController v2 #25915

mcmire opened this issue Jul 17, 2024 · 0 comments · Fixed by #28054
Assignees
Labels
release-12.8.0 Issue or pull request that will be included in release 12.8.0 team-extension-platform team-wallet-framework

Comments

@mcmire
Copy link
Contributor

mcmire commented Jul 17, 2024

What is this about?

Following the Wallet Framework team's OKRs for Q3 2024, we want to bring AlertController up to date with our latest controller patterns.

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

  • A constant called controllerName exists which holds the name of the controller.
  • A constant called controllerMetadata exists which holds the metadata for the state.
  • The default state object is wrapped in a function called getDefaultAlertControllerState.
  • AlertController inherits from BaseController.
    • The AlertController constructor signature is updated to take a partial state (instead of initState) and messenger (instead of controllerMessenger).
    • The AlertController constructor is updated to super to the superclass.
    • AlertController uses this.messagingSystem to refer to the messenger.
    • this.state is used to access state instead of this.store.getState.
    • this.update is used to update state instead of this.store.updateState.
  • Supporting types exist.
    • The AlertControllerState type exists and represents the current shape of the state object.
    • The AlertControllerGetStateAction and AlertControllerStateChangeEvent types exist.
    • The AlertControllerActions and AlertControllerEvents types exist.
    • The AllowedActions and AllowedEvents types exist.
    • The AlertControllerMessenger type exists and expects AccountsController:getSelectedAccount and AccountsController:selectedAccountChange to be allowed.
  • The functionality supported by this controller still works. (There are no tests for this controller, so that may have to be checked manually.)

Stakeholder review needed before the work gets merged

  • Engineering (needed in most cases)
  • Design
  • Product
  • QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
  • Security
  • Legal
  • Marketing
  • Management (please specify)
  • Other (please specify)

References

@mcmire mcmire changed the title Convert AlertController to TypeScript, and migrate to BaseController v2 Migrate AlertController to BaseController v2 Jul 18, 2024
@itsyoboieltr itsyoboieltr self-assigned this Aug 22, 2024
@kanthesha kanthesha self-assigned this Oct 21, 2024
@metamaskbot metamaskbot added the release-12.8.0 Issue or pull request that will be included in release 12.8.0 label Nov 1, 2024
kanthesha added a commit that referenced this issue Nov 1, 2024
<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**
Following the [Wallet Framework team's OKRs for Q3
2024](https://docs.google.com/document/d/1JLEzfUxHlT8lw8ntgMWG0vQb5BAATcrYZDj0wRB2ogI/edit#heading=h.kzzai3cfecro),
we want to bring AlertController up to date with our latest controller
patterns.
<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/28054?quickstart=1)

## **Related issues**

Fixes: #25915 

## **Manual testing steps**

1. Go to this page...
2.
3.

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-12.8.0 Issue or pull request that will be included in release 12.8.0 team-extension-platform team-wallet-framework
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants