-
Notifications
You must be signed in to change notification settings - Fork 364
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
Add Usage page in teams layout (chakra) #4459
Add Usage page in teams layout (chakra) #4459
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Your org has enabled the Graphite merge queue for merging into mainAdd the label “merge-queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @MananTank and the rest of your teammates on Graphite |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4459 +/- ##
=======================================
Coverage 47.76% 47.76%
=======================================
Files 1014 1014
Lines 53277 53277
Branches 3701 3701
=======================================
Hits 25446 25446
Misses 27147 27147
Partials 684 684
*This pull request uses carry forward flags. Click here to find out more. |
size-limit report 📦
|
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.
nice - would be good to split it into "rendering" and "data fetching" -> that way we can re-use the UI but fetch in RSC for teams
Merge activity
|
## Problem solved Short description of the bug fixed or feature added <!-- start pr-codex --> --- ## PR-Codex overview The focus of this PR is to refactor the settings usage page in the dashboard app. ### Detailed summary - Refactored usage page to use `SettingsUsagePage` component - Removed redundant imports and code in `usage.tsx` - Updated `Page` component to render `SettingsUsagePage` - Updated `getLayout` and `pageId` in `Page` component > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
0bf74bc
to
0978bef
Compare
f83e9fa
to
7dd2869
Compare
Problem solved
Short description of the bug fixed or feature added
PR-Codex overview
The focus of this PR is to refactor the settings usage page in the dashboard app.
Detailed summary
UsagePage
component toSettingsUsagePage
usage/page.tsx
UsagePage.tsx
usage.tsx