feat(ramp): enable buy button in asset overview

wachunei commented 3 days ago

Description

This PR adds the buy button to the Token (AssetOverview) page, using the Ramp Intent parameters to optimistically open the Buy flow with the token selected. The Buy button will show if the network is supported.

Happy Path / Optimistic case description:

Given:

The user has already started the Buy flow before and has a region selected from a previous interaction
The asset is supported in the current region and payment method the user has selected from the previous buy flow interaction

Then:

As a user, I want to press the Buy button from the Token page and have the token selected on the Buy flow

Other cases:

If the user has not started the buy button, not selected a region
- Then the user will land on the buy flow start page or region selector
If the asset is not supported in the current region/payment method configuration
- Then the user will land on the buy flow and the default token will be selected.

Related issues

Fixes:

Manual testing steps

Go to Token page
Click on the Buy button

Screenshots/Recordings

Before

No Buy button

https://github.com/user-attachments/assets/7f32aa08-7fda-4cdb-b49b-a2ea5f2a7223

After

Happy Path

https://github.com/user-attachments/assets/0f52cc48-af01-45cb-bc07-503fbcf82d62

Token unavailable (default token is selected)

https://github.com/user-attachments/assets/578fbbbd-e39a-4c79-981e-6139ef7cfef4

Pre-merge author checklist

[x] I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
[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 format if applicable
[x] 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.

github-actions[bot] commented 3 days ago

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: be7c8187872c7b5f0cc43840d3499d56b846a51d Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/ecc227aa-7fef-4311-8ad0-133f14cc26a6

[!NOTE]

This comment will auto-update when build completes

You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request