Skip to content
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

Merged
merged 2 commits into from
Feb 17, 2025

Conversation

thornbill
Copy link
Member

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

@thornbill thornbill added the cleanup Cleanup of legacy code or code smells label Feb 14, 2025
@thornbill thornbill added this to the v10.11.0 milestone Feb 14, 2025
@thornbill thornbill requested a review from a team as a code owner February 14, 2025 20:31
@jellyfin-bot
Copy link
Collaborator

jellyfin-bot commented Feb 14, 2025

Cloudflare Pages deployment

Latest commit ce8bc96
Status ✅ Deployed!
Preview URL https://47ea6e9e.jellyfin-web.pages.dev
Type 🔀 Preview

View build logs

@@ -44,15 +47,21 @@ const TablePage = <T extends MRT_RowData>({
height: '100%'
}}
>
<Box
<Stack
spacing={2}
sx={{
marginBottom: 1
}}
>
<Typography variant='h2'>
Copy link
Member

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?

Copy link
Member Author

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. 🤷‍♂️

@thornbill thornbill merged commit a367e61 into jellyfin:master Feb 17, 2025
15 checks passed
@thornbill thornbill deleted the api-keys-table-page branch February 17, 2025 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Cleanup of legacy code or code smells
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants