-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 api keys to use TablePage component #6526
Conversation
Cloudflare Pages deployment
|
@@ -44,15 +47,21 @@ const TablePage = <T extends MRT_RowData>({ | |||
height: '100%' | |||
}} | |||
> | |||
<Box | |||
<Stack | |||
spacing={2} | |||
sx={{ | |||
marginBottom: 1 | |||
}} | |||
> | |||
<Typography variant='h2'> |
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 wondering, since we seem to be using h2 for the table pages while h1 for the other pages (branding, logs), should either be changed to match?
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 used h2
for the table pages to have more room for the table data on screen... I'm not opposed to doing the same on the other pages. 🤷♂️
|
Changes
Small refactor to update the API keys page to also use the new
<TablePage>
component and a couple miscellaneous driveby cleanup items 🙃Issues
N/A