You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
refactor(mosaic): remove skeleton state from Section - #10325
Stacked on #10323. Removes the old skeleton approach (greying out the real view with Section.Group skeleton) now that skeletons are separate <feature>.skeleton.tsx components swapped in by whatever owns the loading state.
Section.Group no longer takes skeleton, and no longer makes itself inert / aria-hidden or provides skeleton context. It always renders as role='group'.
SkeletonContext is removed. Skeleton always shows unless show={false}.
The active devices skeleton drops its show props and its wrapper div.
Swingset: the Section Loading story now swaps a separate skeleton for the loaded section, keeping the title as real text. The Section and Skeleton docs match.
docs/skeletons.md describes the intended usage: a separate skeleton component, real text for known titles, bones only for fetched content, and fallback only while Clerk loads.
No @clerk/mosaic exports change.
Checklist
pnpm test runs as expected.
pnpm build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 2 remain after this review.
📝 Walkthrough
The changes remove context-based visibility inheritance from Skeleton and skeleton rendering support from Section.Group. The active-devices model now distinguishes device loading from general loading and renders a dedicated skeleton until device data is ready. Tests cover loading, remounting, and session changes. Documentation and stories describe separate skeleton and loaded views, placeholder content, and status announcements.
The loading-state refactor is mergeable after normal checks; no concrete remaining compatibility issue was found.
Pre-merge checks: 4 · 1
Failed checks: 1 warning
Check name
Status
Explanation
Resolution
Docstring Coverage
Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 9 functions across 10 files. (5 skipped: 5…
Write docstrings for the functions missing them to satisfy the coverage threshold.
Passed checks: 4 passed
Check name
Status
Explanation
Title check
The title clearly and concisely describes the primary change: removing skeleton state from Section.
Description check
The description directly explains the removal of the legacy Section skeleton approach and the related Mosaic, active-devices, Swingset, and documentation changes.
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 9 functions across 10 files. (5 skipped: 5 unsupported.)
Resolution
Write docstrings for the functions missing them to satisfy the coverage threshold.
✨ Finishing Touches: 💡 1
⚔️ Resolve merge conflicts: 💡
Resolve merge conflict in branch carp/mosaic-skeleton-cleanup
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
Linked repositories: Some configured repositories could not be included in this review. Cross-repository analysis may be incomplete. Please check linked-repository access and settings.
Comment @coderabbitai help to get the list of available commands.
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
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.
Description
Stacked on #10323. Removes the old skeleton approach (greying out the real view with
Section.Group skeleton) now that skeletons are separate<feature>.skeleton.tsxcomponents swapped in by whatever owns the loading state.Section.Groupno longer takesskeleton, and no longer makes itselfinert/aria-hiddenor provides skeleton context. It always renders asrole='group'.SkeletonContextis removed.Skeletonalways shows unlessshow={false}.showprops and its wrapperdiv.Loadingstory now swaps a separate skeleton for the loaded section, keeping the title as real text. The Section and Skeleton docs match.docs/skeletons.mddescribes the intended usage: a separate skeleton component, real text for known titles, bones only for fetched content, andfallbackonly while Clerk loads.No
@clerk/mosaicexports change.Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change