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

feat: Adding token value field typed sign data tree. #13223

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

jpuri
Copy link
Contributor

@jpuri jpuri commented Jan 28, 2025

Description

Created token value component for typed sign data tree.

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/4034

Manual testing steps

  1. Go to test dapp
  2. Submit permit / seaport request
  3. Check token value in data tree

Screenshots/Recordings

Screen.Recording.2025-01-28.at.5.52.26.PM.mov

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.

@jpuri jpuri added the team-confirmations Push issues to confirmations team label Jan 28, 2025
@jpuri jpuri requested review from a team as code owners January 28, 2025 12:44
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.

Base automatically changed from date_component_support to main January 28, 2025 17:59
@github-actions github-actions bot requested a review from a team as a code owner January 28, 2025 17:59
@jpuri jpuri requested review from a team as code owners January 29, 2025 04:26
@jpuri jpuri changed the base branch from main to text_tooltip January 29, 2025 04:58
github-merge-queue bot pushed a commit that referenced this pull request Jan 29, 2025
## **Description**

PR is adding text with tooltip component as displayed in image below.
This is used in next PR:
#13223

## **Related issues**

Ref: MetaMask/MetaMask-planning#4034

## **Manual testing steps**

1. Run storybook
2. Check the component added

## **Screenshots/Recordings**


https://github.com/user-attachments/assets/9e455e3c-724f-4453-adac-41fa5cf41487

## **Pre-merge author checklist**

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

## **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.
Base automatically changed from text_tooltip to main January 29, 2025 10:12
Copy link
Contributor

@georgewrmarshall georgewrmarshall left a comment

Choose a reason for hiding this comment

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

Hey @jpuri, I'm not sure why the @MetaMask/design-system-engineers were tagged as codeowners for this PR, but I'm approving to unblock. Please still seek reviews from the relevant folks. 🙏

@jpuri jpuri added the Run Smoke E2E Triggers smoke e2e on Bitrise label Jan 30, 2025
Copy link
Contributor

github-actions bot commented Jan 30, 2025

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 7008757
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/7ce7d04c-e3bb-4d59-b9c3-3f8056996231

Note

  • 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

nickewansmith pushed a commit that referenced this pull request Jan 30, 2025
## **Description**

PR is adding text with tooltip component as displayed in image below.
This is used in next PR:
#13223

## **Related issues**

Ref: MetaMask/MetaMask-planning#4034

## **Manual testing steps**

1. Run storybook
2. Check the component added

## **Screenshots/Recordings**


https://github.com/user-attachments/assets/9e455e3c-724f-4453-adac-41fa5cf41487

## **Pre-merge author checklist**

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

## **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
Run Smoke E2E Triggers smoke e2e on Bitrise team-confirmations Push issues to confirmations team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants