Skip to content

Conversation

@digiwand
Copy link
Contributor

@digiwand digiwand commented Jul 23, 2024

Description

Cherry-pick #25769 for Version v12.2.0

looks like I can't merge another cherry-pick into this PR. The test-api-spec test would be fixed after cherry-picking this PR
#26048

Open in GitHub Codespaces

Related issues

Fixes: #24614

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

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.

<!--
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.
-->

This migration sets redesignedConfirmationsEnabled to true. Some users
may have explicitly turned off the experimental setting, which this
migration will reset to true. This is intentional as we also plan to
remove the setting in an upcoming release.

I also added the redesigned confirmation prop to the Sentry state log.
Needed to add or not add it to support the setting in the tests. I went
with adding it.

---

Getting the tests to pass were a bit tricky. It turns out the migrations
run after the fixtures are set. The withPreferencesController fixture
method is no help here.

One way we discussed to set the desired test state is to set the
previous migration data to the state and setting the fixture migration
version to the current version:
```
meta: { version: 122 }
```

This would require opening a live version, extracting the latest
migration state, and adding the mock state to the tests.

Instead, we manually toggle the setting off for each test that requires
the old signature pages.

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

Fixes: #24614

1. Turn off the Experimental > Improved signature redesign setting
2. Run newest version with migration
3. Observe setting has been turned on

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

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

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

- [ ] 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).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] 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.

- [ ] 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.
@digiwand digiwand requested review from a team as code owners July 23, 2024 13:34
@github-actions
Copy link
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@digiwand digiwand added team-confirmations Push issues to confirmations team release-12.2.0 Issue or pull request that will be included in release 12.2.0 labels Jul 23, 2024
Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

This pull request enables redesigned confirmations for all users by default and includes necessary migration and test updates.

  • Migration Script: Added app/scripts/migrations/122.ts to set redesignedConfirmationsEnabled to true.
  • Unit Tests: Introduced app/scripts/migrations/122.test.ts to validate the migration.
  • E2E Tests: Updated multiple E2E test files to include tempToggleSettingRedesignedConfirmations for testing the new feature.
  • Sentry Integration: Modified app/scripts/lib/setupSentry.js to include the new preference in error reporting.
  • UI Update: Added data-testid attribute in ui/pages/settings/experimental-tab/experimental-tab.component.tsx for testing purposes.

19 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings

@digiwand digiwand linked an issue Jul 23, 2024 that may be closed by this pull request
@digiwand digiwand requested review from a team, matthewwalsh0 and pedronfigueiredo July 23, 2024 15:52
@digiwand
Copy link
Contributor Author

closing as we cannot update PR to resolve conflicts and accept test api-spec fixes due to branch naming. New PR: #26139

@digiwand digiwand closed this Jul 25, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jul 25, 2024
@HowardBraham HowardBraham deleted the Version-v12.2.0-feat-migration-122-redesignedConfirmationsEnabled-3 branch July 4, 2025 05:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

release-12.2.0 Issue or pull request that will be included in release 12.2.0 team-confirmations Push issues to confirmations team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enable redesigned signatures for all users.

6 participants