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: Implement staking details section #13475

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

pedronfigueiredo
Copy link
Contributor

@pedronfigueiredo pedronfigueiredo commented Feb 13, 2025

Description

Adds hook that encapsulates the component logic, and unit tests.

Related issues

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

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

Before

After

Screenshot 2025-02-13 at 12 37 26

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.

@pedronfigueiredo pedronfigueiredo added the team-confirmations Push issues to confirmations team label Feb 13, 2025
@pedronfigueiredo pedronfigueiredo self-assigned this Feb 13, 2025
@pedronfigueiredo pedronfigueiredo requested review from a team as code owners February 13, 2025 12:22
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.

@pedronfigueiredo pedronfigueiredo added the Run Smoke E2E Triggers smoke e2e on Bitrise label Feb 13, 2025
Copy link
Contributor

github-actions bot commented Feb 13, 2025

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: e711cf0
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/9a25c692-1d96-4e21-96a6-d7f6490a0ade

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

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.

1 participant