fix: use zero swap amount from assets table [SWAP-83]

schmanu commented 2 months ago

What it solves

SWAP-83

How this PR fixes it

Sets amount to 0

How to test it

Click on swap button on assets list

Checklist

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

notion-workspace[bot] commented 2 months ago

Set swap amount to 0 from assets page

github-actions[bot] commented 2 months ago

Branch preview

✅ Deploy successful!

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

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

github-actions[bot] commented 2 months ago

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: :white_check_mark: success
- Annotations: 0 total

^{Report generated by eslint-plus-action}

github-actions[bot] commented 2 months ago

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

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

One Page Changed Size

The following page changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
`/balances`	`29.17 KB` (🟢 -21 B)	1.05 MB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

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

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

github-actions[bot] commented 2 months ago

Coverage report

St.^{:grey_question:}	Category	Percentage	Covered / Total
🟡	Statements	79.28% (-0.12% 🔻)	11627/14665
🔴	Branches	58.14% (-0.3% 🔻)	2751/4732
🟡	Functions	66.38% (-0.19% 🔻)	1866/2811
🟢	Lines	80.62% (-0.12% 🔻)	10478/12996

Show files with reduced coverage 🔻

|

St.^{:grey_question:}

| File | Statements | Branches | Functions | Lines | | :-: | :- | :- | :- | :- | :- | | 🟢 |

`...` / index.tsx

|

96.15% (-3.85% 🔻)

|

87.5% (-12.5% 🔻)

| 100% |

95.65% (-4.35% 🔻)

| | 🟢 |

`...` / tx-history-filter.ts

| 100% |

85.71% (-2.86% 🔻)

| 100% | 100% | | 🟢 |

`...` / index.tsx

|

96.67% (-0.05% 🔻)

| 72.22% | 76.92% |

96.55% (-0.06% 🔻)

|

Test suite run success

1468 tests passing in 202 suites.

Report generated by 🧪jest coverage report action from d6e2260655729b0bded5532f31cc0389b76e833e

francovenica commented 2 months ago

LGTM

safe-global / safe-wallet-web