Conversation
Owner
Author
|
Closed because this draft was created in the fork by mistake. Recreated against tracefinity/tracefinity as tracefinity#138. |
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
This adjusts dashboard collapse defaults so important content is visible when users first land on the main dashboard and project pages.
The PR keeps user-controlled collapse behavior, but resets the persisted storage keys so older saved collapsed states do not force sections closed after this change.
The intended defaults are:
Implementation Notes
The previous collapse state was persisted under:
tracefinity.home.collapsedSectionstracefinity.project.collapsedSectionsThis PR moves those to versioned keys:
tracefinity.home.collapsedSections.v2tracefinity.project.collapsedSections.v2That gives users the new defaults on first load after the update, while still remembering any collapse/expand choices they make afterward.
Bin Defaults remains collapsed by default because it is lower-frequency configuration. Project Tools and Linked Bins are expanded because they are the primary project contents users expect to see after adding tools or bins.
Tests
corepack pnpm@10.29.2 --dir frontend lintcorepack pnpm@10.29.2 --dir frontend exec tsc --noEmitCode and PR drafted with Codex