-
Notifications
You must be signed in to change notification settings - Fork 428
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
Refactor: generate terms page from md file #4183
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.92 KB (🟡 +14.4 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!
Twenty-five Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load |
---|---|---|
/address-book |
26.1 KB (🟡 +1 B) |
980.02 KB |
/apps |
50.18 KB (-5 B) |
1004.1 KB |
/apps/custom |
41.81 KB (🟢 -8 B) |
995.74 KB |
/apps/open |
54.73 KB (🟡 +1 B) |
1008.65 KB |
/balances |
30.66 KB (🟢 -7 B) |
984.58 KB |
/balances/nfts |
19.18 KB (🟢 -5 B) |
973.1 KB |
/home |
60.21 KB (-2 B) |
1014.14 KB |
/new-safe/advanced-create |
35.14 KB (-3 B) |
989.07 KB |
/new-safe/create |
34.41 KB (🟡 +1 B) |
988.33 KB |
/new-safe/load |
16.41 KB (🟢 -2 B) |
970.34 KB |
/settings/cookies |
7.66 KB (🟢 -1 B) |
961.59 KB |
/settings/data |
7.56 KB (🟢 -1 B) |
961.49 KB |
/settings/environment-variables |
9.15 KB (🟢 -3 B) |
963.07 KB |
/settings/safe-apps |
25.56 KB (-1 B) |
979.49 KB |
/settings/security |
8.08 KB (🟢 -1 B) |
962.01 KB |
/settings/setup |
35.98 KB (🟢 -5 B) |
989.9 KB |
/share/safe-app |
9.72 KB (🟡 +1 B) |
963.65 KB |
/stake |
602 B (🟡 +1 B) |
954.51 KB |
/terms |
544 B (🟢 -10.66 KB) |
954.46 KB |
/transactions |
73.52 KB (-2 B) |
1 MB |
/transactions/history |
73.48 KB (-3 B) |
1 MB |
/transactions/messages |
39.16 KB (-4 B) |
993.08 KB |
/transactions/msg |
29.51 KB (-2 B) |
983.43 KB |
/transactions/tx |
21.06 KB (🟡 +1 B) |
974.99 KB |
/welcome |
6.77 KB (🟢 -2 B) |
960.7 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 success1485 tests passing in 203 suites. Report generated by 🧪jest coverage report action from 93aca16 |
3b11d43
to
7ec4e2b
Compare
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.
Looks great but we should move some (all?) of these new dependencies in devDependencies. Nonce of them seem to be imported in any runtime module.
ce857e2
to
3a4d36c
Compare
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 cookie banner now shows the last updated version. In addition to this it is no longer necessary to update the version number inside of the store slice. We can control it from the frontmatter of the terms.md doc. Whenever the version gets updated the cookie banner is going to pop up.
3a4d36c
to
44003f3
Compare
ESLint Summary View Full Report
Report generated by eslint-plus-action |
44003f3
to
93aca16
Compare
What it solves
It's very cumbersome to update the Terms page as it is in html and we have to find the changed areas and make sure to correctly update them. Instead with this change we can always export the complete terms document to md and then leave it to remark to render it as html
Resolves #
How this PR fixes it
How to test it
Screenshots
Checklist