Skip to content

Conversation

@runway-github
Copy link
Contributor

@runway-github runway-github bot commented Oct 29, 2025

Description

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

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.

Note

Adds legal consent checkboxes with deep-linked disclosures to the Physical Address step, enforces country-specific consent validation, updates types/translations, and expands tests.

  • Card Onboarding (UI/Logic):
    • Physical Address (PhysicalAddress.tsx):
      • Adds US and Intl legal consent checkboxes (e-sign, account opening disclosure, terms, privacy, right to information) with tappable links via Linking.
      • Introduces country-specific validation gating the Continue button on required consents.
      • Stores and toggles consent states; opens respective URLs from registrationSettings.links.
  • Types:
    • Extends RegistrationSettingsResponse.links.us with eSignConsentDisclosure in app/components/UI/Card/types.ts.
  • i18n:
    • Adds/updates onboarding consent strings in locales/languages/en.json (terms, privacy, right to information, account opening disclosure; tweaks electronic consent key/text).
  • Tests:
    • Updates/expands PhysicalAddress.test.tsx to cover consent visibility (US vs Intl), toggling, and validation requiring all consents; mocks useDispatch and new links.
    • Minor updates in MailingAddress.test.tsx to include new eSignConsentDisclosure in mocked settings.

Written by Cursor Bugbot for commit c9d5dbc. This will update automatically on new commits. Configure here.

7d80805

…21814)

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

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

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: null

Fixes:

```gherkin
Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]
```

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

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

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

- [x] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.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-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

- [x] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [x] 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.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Adds country-specific legal consent checkboxes with deep-linked
disclosures to the Physical Address step, enforces them in form
validation, updates types/i18n, and expands tests.
>
> - **UI — Card Onboarding (`PhysicalAddress.tsx`)**:
> - Add consent checkboxes and links: US (electronic consent, account
opening disclosure, terms, privacy) and Intl (terms, right to
information).
> - Open disclosure URLs via `Linking` using values from
`registrationSettings.links`.
> - Gate "Continue" by required consents per country; update
label/translation keys.
> - **Types (`app/components/UI/Card/types.ts`)**:
> - Extend `RegistrationSettingsResponse.links.us` with
`eSignConsentDisclosure`.
> - **i18n (`locales/languages/en.json`)**:
>   - Add consent-related strings; adjust electronic consent text.
> - **Tests**:
> - Expand `PhysicalAddress.test.tsx` for consent visibility/toggles,
validation, and navigation flows; mock `eSignConsentDisclosure`.
> - Minor test adaptations (key rename, `useDispatch` mock) and settings
mocks in mailing/physical address tests.
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
e40edbb. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
@runway-github runway-github bot requested a review from a team as a code owner October 29, 2025 00:35
@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.

@metamaskbot metamaskbot added the team-bots Bot team (for MetaMask Bot, Runway Bot, etc.) label Oct 29, 2025
@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
60.7% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

Copy link
Contributor

@Cal-L Cal-L left a comment

Choose a reason for hiding this comment

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

LGTM

@Cal-L Cal-L merged commit f1ecb56 into release/7.58.0 Oct 29, 2025
83 of 88 checks passed
@Cal-L Cal-L deleted the cherry-pick-7-58-0-7d80805 branch October 29, 2025 04:10
@github-actions github-actions bot locked and limited conversation to collaborators Oct 29, 2025
@metamaskbot metamaskbot added the release-7.58.0 Issue or pull request that will be included in release 7.58.0 label Oct 29, 2025
@metamaskbot
Copy link
Collaborator

No release label on PR. Adding release label release-7.58.0 on PR, as PR was cherry-picked in branch 7.58.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

release-7.58.0 Issue or pull request that will be included in release 7.58.0 size-M team-bots Bot team (for MetaMask Bot, Runway Bot, etc.)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants