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

chore: cherry-pick #10039 #10059

Merged
merged 2 commits into from
Jun 21, 2024
Merged

Conversation

github-actions[bot]
Copy link
Contributor

This PR cherry-picks #10039

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

## **Description**

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

This PR enables transaction simulation in mobile which is implemented in
the #9828

## **Related issues**

This is the final task for mobile transaction simulation to enable it in
mobile.

## **Manual testing steps**

1. Either go for the simple send or contract interaction
2. See transaction simulations appear in the confirmation screen as
loading state first - then simulates the transaction

## **Screenshots/Recordings**

Recording could be found in the original implementation PR:
#9828

## **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.

---------

Co-authored-by: LeoTM <1881059+leotm@users.noreply.github.com>
Copy link
Contributor

@NicolasMassart NicolasMassart left a comment

Choose a reason for hiding this comment

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

Looks good to me: this cherry pick matches the original PR.

@NicolasMassart NicolasMassart marked this pull request as ready for review June 21, 2024 10:33
@NicolasMassart NicolasMassart requested review from a team as code owners June 21, 2024 10:33
@NicolasMassart
Copy link
Contributor

@metamaskbot update-attributions

Copy link
Contributor Author

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.

Copy link

sonarcloud bot commented Jun 21, 2024

@NicolasMassart NicolasMassart merged commit c5497a9 into release/7.26.0 Jun 21, 2024
29 checks passed
@NicolasMassart NicolasMassart deleted the chore/cherry-pick-10039 branch June 21, 2024 11:27
@github-actions github-actions bot locked and limited conversation to collaborators Jun 21, 2024
@metamaskbot metamaskbot added the release-7.26.0 Issue or pull request that will be included in release 7.26.0 label Jun 21, 2024
@metamaskbot
Copy link
Collaborator

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
release-7.26.0 Issue or pull request that will be included in release 7.26.0 team-mobile-platform
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants