Closed usame-algan closed 2 days ago
β Deploy successful!
Storybook: https://twap_fallback_handler--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 |
1000.18Β KB (π‘ +12Β 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 |
---|---|---|
/settings/modules |
9.74Β KB (π‘ +121Β B) |
1009.92Β KB |
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.76% (+0% πΌ) |
11394/14467 |
π΄ | Branches | 58.04% (-0.01% π») |
2758/4752 |
π‘ | Functions | 65.73% | 1828/2781 |
π’ | Lines | 80.14% (-0% π») |
10268/12813 |
1413 tests passing in 195 suites.
Report generated by π§ͺjest coverage report action from 5e3a2fb7f1e36b3196e744e33078812294d19fa5
@usame-algan can you ask infra to add title and icon as in the figma design? Or we hardcode all of those in the code?
@usame-algan can you ask infra to add title and icon as in the figma design? Or we hardcode all of those in the code?
Good idea! I asked infra to add the fallback handler address to the known contract list.
LGTM Looks like this right now, so I assume infra did give it the proper icon an title
The icon is different than in the designs, but I think CowSwap changed it recently so I think is ok:
@francovenica CoW changed their branding slightly, so I will need to update their logos in our design system. The difference is OK for now.
Could we add rounded corners to the icons? E.g. 4px should be fine
What it solves
Resolves SW-33
How this PR fixes it
How to test it
Screenshots
Checklist