feat: added KeyValueRow to component-library/components-temp

[Matt561]

Description

This PR adds <KeyValueRow /> to the components-temp library. The motivation is to improve DX and reusability since we commonly display a variety of key/value pairs within the app.

What's Included?

1. <KeyValueRow />

• default export to handle majority of common use cases. Example usages have been added to the storybook.

2. KeyValueRowStubs

• <Root />: The main container. Its children should be two <Section /> components representing the left side (key) and right side (value) of the pairing.
• <Section />: A container representing either the key or the value.
• <Label />: A convenience component that provides built-in support for icons, tooltips, and formatting.

3. Updated withNavigation Storybook Decorator

This change was made to support the tooltip modal used within the <KeyValueRow />. I think it's appropriate for the story to accurately reflect the interactivity of the components on display.

This should also allow others to use modals in their stories.

These stubs can be used to extend this and create new variants of the KeyValueRow.

Related issues

STAKE-829: [FE] Create Key Value Row component - link

Manual testing steps

1. Switch to the storybook view (instructions here)
2. Select the KeyValueRow story inside of "Components Temp" folder.
3. Example usages of <KeyValueRow /> found within the story

Screenshots/Recordings

Before

N/A this is a net new change.

After

Design Link

https://www.figma.com/design/1c0Y9jDJe6p0j82jydJDcs/Mobile-Staking?node-id=2187-96037&t=kOEnlk3CXZ727Qjb-1

Storybook Health Check

Storybook is still working after making the withNavigation decorator changes

stake-829-storybook-health-check.mov

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.

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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 3a353a3
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2385d618-f5de-4d93-91ab-edd3a558f789

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 7b8036c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/0bcd5df0-709e-4750-b6fa-b083d2bd7a50

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[brianacnguyen]

Can you provide a Figma link in the comment?

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 120b2b4
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/66d0e771-6f80-4aa2-97a5-bc8227495297

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[Matt561]

Can you provide a Figma link in the comment?

Sure thing! Here's what I used. I don't think it's part of DS yet though.

https://www.figma.com/design/1c0Y9jDJe6p0j82jydJDcs/Mobile-Staking?node-id=2187-96037&t=kOEnlk3CXZ727Qjb-1

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: da9d4f4
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b168438f-af66-460b-8071-726dd6b0f598

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 81.25000% with 9 lines in your changes missing coverage. Please review.

Project coverage is 55.95%. Comparing base (b9dbf4d) to head (a4c66f5).
Report is 26 commits behind head on main.

Files with missing lines	Patch %	Lines
...omponents-temp/KeyValueRow/KeyValueRow.stories.tsx	0.00%	4 Missing ⚠️
...s-temp/KeyValueRow/KeyValueLabel/KeyValueLabel.tsx	83.33%	2 Missing ⚠️
...ibrary/components-temp/KeyValueRow/KeyValueRow.tsx	83.33%	0 Missing and 2 partials ⚠️
...y/components-temp/KeyValueRow/KeyValueRow.utils.ts	50.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #11294      +/-   ##
==========================================
+ Coverage   55.84%   55.95%   +0.10%     
==========================================
  Files        1594     1607      +13     
  Lines       37855    37974     +119     
  Branches     4545     4597      +52     
==========================================
+ Hits        21142    21250     +108     
- Misses      16214    16218       +4     
- Partials      499      506       +7     

Flag	Coverage Δ
	55.95% <81.25%> (+0.10%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: a5f3f07
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/7e698b09-e5cb-4d8a-b336-5bdb562b0b30

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: ad5f60f
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b075ebb8-75e4-4d6e-a353-fdeb0188d8ee

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud