-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat: Kiln widget #3962
Feat: Kiln widget #3962
Conversation
Branch preview✅ Deploy successful! Storybook: |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
📦 Next.js Bundle Analysis for safe-wallet-webThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
Page | Size (compressed) |
---|---|
global |
953.35 KB (🟡 +3.74 KB) |
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!
New Page Added
The following page was added to the bundle from the code in this PR:
Page | Size (compressed) | First Load |
---|---|---|
/stake |
589 B |
953.92 KB |
Thirteen Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load |
---|---|---|
/apps |
50.18 KB (-2 B) |
1003.53 KB |
/apps/custom |
41.79 KB (-2 B) |
995.14 KB |
/apps/open |
54.74 KB (🟡 +1.16 KB) |
1008.09 KB |
/home |
60.25 KB (🟢 -73 B) |
1013.6 KB |
/settings/safe-apps |
25.55 KB (-2 B) |
978.9 KB |
/settings/setup |
35.95 KB (-3 B) |
989.3 KB |
/swap |
723 B (🟡 +77 B) |
954.05 KB |
/transactions |
73.47 KB (🟢 -374 B) |
1 MB |
/transactions/history |
73.43 KB (🟢 -376 B) |
1 MB |
/transactions/messages |
39.12 KB (🟢 -79 B) |
992.47 KB |
/transactions/msg |
29.5 KB (🟢 -79 B) |
982.85 KB |
/transactions/queue |
31.22 KB (🟢 -79 B) |
984.57 KB |
/transactions/tx |
21.05 KB (🟢 -79 B) |
974.4 KB |
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.
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success1484 tests passing in 203 suites. Report generated by 🧪jest coverage report action from 5adb8ea |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
3f1d212
to
18a7357
Compare
18a7357
to
d935b59
Compare
ESLint Summary View Full Report
Report generated by eslint-plus-action |
b443464
to
5d548c5
Compare
5d548c5
to
0192052
Compare
ESLint Summary View Full Report
Report generated by eslint-plus-action |
1860841
to
4b52160
Compare
ESLint Summary View Full Report
Report generated by eslint-plus-action |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
67c9321
to
5f89012
Compare
1f12a94
to
9b864c6
Compare
export const OrderFeeConfirmationView = ({ | ||
order, | ||
}: { | ||
order: Pick<SwapOrderConfirmationView | TwapOrderConfirmationView, 'fullAppData'> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace with AnySwapConfirmationView?
onDismiss={dismissQueueBar} | ||
transactions={transactions} | ||
/> | ||
{!isNativeEmbed && ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a bit unclear why a native Embed wouldn't have the transactionQueueBar. I remember talking to @schmanu and I think he likes the bar and even wanted to have it for the swap feature.
Maybe a more explicit name such as "hideTransactionBar" is more appropriate? But then I see above that we are also removing the page title... and also not emitting tracking events.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think native swaps and native staking are both basically full screen Safe apps. So I do not see a reason to hide the queue bar if there are transactions in the queue.
Especially if some actions require multiple interactions, forcing users to switch context means that likely the widgets will load back into their original state so some context could be lost.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not against keeping it. It's just not consistent with other pages. Why don't we show it on all pages except for the queue itself?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anyway, I removed the check that hides the queue bar.
} | ||
} | ||
|
||
const TokenInfoPair = ({ blocks, showArrow }: { blocks: [InfoBlock, InfoBlock]; showArrow?: boolean }) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That name is a small lie & you know it :)
Maybe a better name would be BlockInfoPair?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe ConfirmationOrderHeader
?
const chainId = useChainId() | ||
const isMethodCallInAdvanced = !showMethodCall || isMultisend | ||
const isMultisend = !!decodedData?.parameters?.[0]?.valueDecoded | ||
const isMethodCallInAdvanced = !showMethodCall || (isMultisend && showMultisend) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The showMultisend here is confusing. Now the name is isMethodCallInAdvanced
, but since showMultisend could be false this would also be false, despite the method call being in advanced. I'm more for havign showMultisend inside of the render.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to make sure we understand the same logic. We move the method name and parameters to Advanced details in two cases:
- When
showMethodCall
is set to false in props - When it's a multi-send and
showMultisend
from props is true
How would you make this less confusing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's leave it like this for now as @clovisdasilvaneto and I are refactoring this more comprehensively.
ESLint Summary View Full Report
Report generated by eslint-plus-action |
@katspaugh , regression issue : According to the design for staking it should not be hidden under the advanced parameters. Could we leave it , as it was previously and leave it according to the expected design - https://www.figma.com/design/ih2mM8bt8rNwbwV9EMmWF5/Staking?node-id=3166-8821&t=koQt4lxTOPWuHFVT-4 Edit by @katspaugh: I've updated the description with a justification for this change + linked to a diagram. ✅ |
Edit by @katspaugh: Fixed ✅ |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
798e334
to
72fbd8f
Compare
ESLint Summary View Full Report
Report generated by eslint-plus-action |
Other changes