feat: render rich text from contentful

[sophieqgu]

Description

Render contentful rich text

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

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• 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 format if applicable
• I've applied the right labels on the PR (see labeling guidelines). 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.

---

Note

Medium Risk
Adds a new rich-text renderer and switches rewards screens to render Contentful-provided documents and open links via in-app browser navigation, which may affect UI rendering and link handling for live campaign content.

Overview
Enables Rewards UI to render Contentful rich text documents (paragraphs, headings, lists, text marks, and hyperlinks) via a new ContentfulRichText component, with hyperlinks opening in the in-app browser.

Updates CampaignMechanicsView to render howItWorks.notes only when it is a valid Contentful document (removing the previous structured-notes parsing and related testIDs), and updates CampaignOptInSheet to prefer campaign.termsAndConditions rich text with a static fallback.

Adds comprehensive unit tests for the new rich-text renderer and adjusts existing tests for the new rendering/navigation behavior.

^{Written by Cursor Bugbot for commit 70a7760. This will update automatically on new commits. Configure here.}

[github-actions]

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.

[cursor]

Cursor Bugbot has reviewed your changes and found 3 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 90%

click to see 🤖 AI reasoning details

E2E Test Selection:
The PR modifies only the Rewards feature UI components:

1. ContentfulRichText.tsx (new file): A new renderer for Contentful CMS rich text documents. Purely a UI utility component scoped to the Rewards feature.

2. CampaignMechanicsView.tsx: Refactored to use ContentfulRichText instead of a custom notes parser. The notes section now renders Contentful documents instead of hardcoded structured data.

3. CampaignOptInSheet.tsx: Updated to support ContentfulRichText for terms & conditions, and changed the terms link handler from Linking.openURL() to in-app browser navigation.

Why no E2E tags are selected:

• None of the available E2E test tags cover the Rewards/Campaigns feature area. There are no E2E test specs referencing CampaignOptInSheet, CampaignMechanicsView, ContentfulRichText, or the Rewards campaign flows.
• The changes are entirely scoped to the Rewards UI feature — no shared infrastructure (TabBar, navigation stack, modals, controllers, Engine) is modified.
• The behavioral change (Linking.openURL → in-app browser navigation) is contained within the Rewards opt-in sheet and doesn't affect any other tested flows.
• The test files changed are unit tests (.test.tsx), not E2E specs.
• No controller, Engine, or core module changes are present.

The risk is low as these are isolated UI component changes with unit test coverage, and no existing E2E tests cover this feature area.

Performance Test Selection:
The changes are limited to UI component refactoring within the Rewards feature. No performance-sensitive code paths are affected: no list rendering changes, no state management modifications, no data loading or API call changes, no account/network selectors, and no app startup/initialization code. The ContentfulRichText component is a simple recursive renderer for CMS content, not a performance-critical path.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
86.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud