Repository navigation
Keep one sidebar entry for Codex borrowing pages - #261
Merged
Merged
Conversation
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
1 participant
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.
Keep one Codex Borrowing entry in the Extensions sidebar. Settings, route status and pelican comparison remain separate pages reached through the existing in-page navigation, and all three pages highlight the same sidebar entry. Keep the settings page's specific document/header title independent of the umbrella sidebar label.
Validation: the seven focused sidebar visibility/order/active-route cases, changed-file ESLint, three locale completeness checks, Vue/TypeScript checking and production build passed. One desktop synthetic browser scenario confirmed a single active sidebar entry on all three routes, functioning in-page links and page-specific header/document titles; all observed API requests were local GETs. No backend, account configuration, model/probe, or generation behavior changes.