Closed compojoom closed 1 month ago
β Deploy successful!
Storybook: https://fix_token_reset_on_tradetype_change--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 |
950.04Β KB (π‘ +2Β 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 |
29.17Β KB (π‘ +73Β B) |
979.2Β 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 | 79.47% | 11295/14213 |
π΄ | Branches | 58.46% | 2699/4617 |
π‘ | Functions | 66.67% | 1822/2733 |
π’ | Lines | 80.85% | 10185/12597 |
1436 tests passing in 197 suites.
Report generated by π§ͺjest coverage report action from bd7bfc2d247855905e02cf4a1961feee75178196
Question. I see it here as it is in QA in the CowSwap board in notion, but is not currently in the github board, any reason no not having it there?
I've checked and the tokens are preserverd when switching from the "Swap" form to the "limits" form, so that's correct
Question since it's not in the ticket description and it might be out of the scope: The values seems to not be maintained. is this intended? I tried to see in the original cowswap app, but currently it seems to be having problems (is not connecting the wallet and it is working really slow) so I cannot check right now
Question. I see it here as it is in QA in the CowSwap board in notion, but is not currently in the github board, any reason no not having it there?
Only because our workflows suck... And I have to do the same things twice
Question since it's not in the ticket description and it might be out of the scope: The values seems to not be maintained. is this intended?
I wanted to also maintain the values, but the swap widget behaves strange there. It seems to keep separate values for swap and limit, so it doesn't apply the swap value to limit and vice versa. I'll ask @anxolin about this.
What it solves
When switching betwenn Swap/Limit forms, selected tokens are reset. On CoW Swap they are synced between all forms.
How this PR fixes it
We were re-rendering the widget when the user switches between swap and a limit swap and this was causing the sellToken to reset. Now, we no longer do this
How to test it
Screenshots
Checklist