Repository navigation
docs(api): put APIs at menu root, clarify nesting (v5.4 backport of #4708) - #4713
Open
JorisHeadease wants to merge 1 commit into
Open
JorisHeadease wants to merge 1 commit into
JorisHeadease wants to merge 1 commit into
Conversation
Backport of #4708 to V5.4, adapted because V5.4 has no deprecated APIs: dropping x-tagGroups moves the APIs from the single "APIs" group to the menu root, so no Deprecated tag and no breadcrumb rule are needed. Custom CSS gives nested objects and expanded responses a stronger line and a tint per level, as on master.
JorisHeadease
marked this pull request as ready for review
November 17, 2026 16:40
reinkrul
approved these changes
Nov 17, 2026
This branch has not been deployed
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.
Backport of #4708 to V5.4.
V5.4 has no deprecated APIs, so its menu had a single "APIs" group. Dropping
x-tagGroupsmoves the APIs to the menu root, and no Deprecated tag orparentis needed. Without nested tags Scalar shows no breadcrumb bar, so the rule that hides it on master is left out. The CSS for nested objects and expanded responses, anddefaultOpenFirstTag: false, are the same as on master.Verified on this branch: the merge script combines the specs into 56 operations, with 13 menu items at the root and links to tags and operations unchanged. Nested objects and expanded responses get the tint while collapsed panels don't, and Sphinx builds with the same 14 warnings as before.