Repository navigation
Show viewed settings first in the sidebar menu - #1754
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
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.
Newly opened viewed-object sidebars now start with their own discovered settings rather than the native Thread connection-status panel. The existing ThreadSidebar composition yields the view's configuration declarations first, followed by its inherited role panels. No label list, preferred-title lookup or new default flag.
PanelMenu still restores the user's retained nominal panel selection before considering the first entry. This changes the initial presentation only; explicit selection, lazy form construction, ObjectState inheritance and native role-panel behavior are unchanged. The existing channel/file/native/context UI control passed on the preceding coherent change. This two-line ordering correction is established by the complete composition-to-selection trace; no extra test suite or profiler was run.