Open schmanu opened 3 days ago
β Deploy successful!
Storybook: https://fix_amounts--walletweb.review.5afe.dev/storybook/
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 |
Report generated by eslint-plus-action
This analysis was generated by the Next.js Bundle Analysis action. π€
Page | Size (compressed) |
---|---|
global |
999.98Β KB (π’ -209Β B) |
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!
The following page changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load |
---|---|---|
/swap |
30.45Β KB (π‘ +365Β B) |
1.01Β MB |
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.
St.:grey_question: |
Category | Percentage | Covered / Total |
---|---|---|---|
π‘ | Statements | 78.71% (-0.04% π») |
11386/14465 |
π΄ | Branches | 57.95% (-0.09% π») |
2753/4751 |
π‘ | Functions | 65.66% (-0.07% π») |
1828/2784 |
π’ | Lines | 80.09% (-0.05% π») |
10261/12812 |
1416 tests passing in 195 suites.
Report generated by π§ͺjest coverage report action from ccb4117eb47026c258f722b9cc8ed05facf03bad
A more general observation: It is not clear what amount format components like SendAmountBlock
expect. For example if I want to send 1 ETH
, the component expects the value to be 1
and not 1
with 18 zeroes but this is not clear from looking at its props. Imo we should find a way to define this either via types or naming so that regressions are less likely to happen.
What it solves
On some locales native values are displayed as NaN.
How this PR fixes it
Always uses
safeFormatUnits
instead offormatVisualAmount
before passing the value toSendAmountBlock
Checklist