Feat: staking claim [SW-160]

[compojoom]

What it solves

Ads decoding views for stake claim txs

Resolves #

How this PR fixes it

How to test it

Screenshots

Checklist

• I've tested the branch on mobile 📱
• I've documented how it affects the analytics (if at all) 📊
• I've written a unit/e2e test for it (if applicable) 🧑‍💻

[notion-workspace]

Native staking: Claim rewards (=Withdraw)

[github-actions]

Branch preview

✅ Deploy successful!

Website:
https://feat_staking_claim--walletweb.review.5afe.dev/home?safe=eth:0xA77DE01e157f9f57C7c4A326eeE9C4874D0598b6

Storybook:
https://feat_staking_claim--walletweb.review.5afe.dev/storybook/

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[github-actions]

📦 Next.js Bundle Analysis for safe-wallet-web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page	Size (compressed)
global	953.62 KB (🟡 +279 B)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	78.23% (-0.03% 🔻)	11956/15284
🔴	Branches	58.19% (-0.11% 🔻)	3053/5247
🟡	Functions	65.35% (-0.08% 🔻)	1888/2889
🟡	Lines	79.73% (-0.01% 🔻)	10792/13536

Show new covered files 🐣

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / index.tsx	75%	100%	0%	100%
🟢	... / index.tsx	80%	100%	0%	100%
🟢	... / Withdraw.tsx	83.33%	100%	0%	100%

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟡	... / transaction-guards.ts	69.27% (-1% 🔻)	33.87% (-2.34% 🔻)	67.8% (-0.62% 🔻)	70.68% (-1.2% 🔻)
🟡	... / extractTxInfo.ts	68.75%	37.74% (-1.48% 🔻)	100%	68.09%
🟢	... / index.tsx	87.5% (+0.66% 🔼)	38.24% (-1.16% 🔻)	50%	86.84% (+0.73% 🔼)
🔴	... / index.tsx	42.86% (-2.6% 🔻)	0%	0%	46.15% (-3.85% 🔻)
🟡	... / useTransactionType.tsx	60.87% (-1.35% 🔻)	36.96% (-0.82% 🔻)	100%	61.36% (-1.43% 🔻)

Test suite run success

1484 tests passing in 203 suites.

Report generated by 🧪jest coverage report action from 5d8367f

[katspaugh]

Can’t these titles be deduced from the txInfo/txConfirmation type?

[compojoom]

As discussed in the call - we currently do this because the app title is a component that is rendered before the modal content and as such it doesn't have access to the txInfo. This would need a refactoring (since you guys are working on the txflow #4157 you can consider it there)

[katspaugh]

Tested, it works correctly ✅

Tx comfirmation:

Tx details in the queue:

I'm not convinced it's a good idea to say "Receive" in one place but "Amount" in another for the exact same thing (rewards mount). @TanyaEfremova shall we unify the phrasing maybe?

[katspaugh]

@compojoom also I would make the gap between these two blocks a tiny bit bigger (notice that the space above Receive is bigger than below):

[TanyaEfremova]

@katspaugh You're right, it's not intended to say 'Amount'. Both screens (transaction summary and transaction confirmation) are now aligned in Figma.