fix(admin): entries form & schema builder UI polish, sticky toolbar, branded loader#61
Merged
Merged
Conversation
… and Entries pages
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
… PR in package.json
faisal-rx
approved these changes
May 22, 2026
… PR in pnpm-lock.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cluster of admin-side UI fixes for the Entries forms, Schema Builder, sidebar, and global permission-loading state. Most user-visible: field widths are now respected across nested groups / components / builder rows, the Schema Builder toolbar stays pinned while scrolling, the Entries table no longer shows the id column by default, the sidebar stops flashing an empty state on hydration, and PermissionGuard gets a branded glassmorphic loader.
Type of change
[X] Bug fix (non-breaking change which fixes an issue)
[X] UI / polish / refactor (no behaviour change for end users beyond visuals)
Related issues
Changeset
This repo uses Changesets. If your PR changes any publishable package under
packages/*, you must include a changeset:Then commit the generated
.changeset/*.mdfile.apps/*)Test plan
pnpm lintpnpm check-typespnpm buildChecklist
mainbranchScreenshots / recordings
Notes for reviewers