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
Copy file name to clipboardExpand all lines: docs/configure/content-set/api-explorer.md
+30-2Lines changed: 30 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -119,7 +119,7 @@ The API Explorer supports the following OpenAPI specification extensions to enha
119
119
120
120
### `x-displayName` for tags
121
121
122
-
Use the `x-displayName` extension on tag objects to provide user-friendly display names in navigation and landing pages while maintaining stable URLs based on the canonical tag name.
122
+
Use the `x-displayName` extension (from [Redocly](https://redocly.com/docs-legacy/api-reference-docs/specification-extensions/x-display-name)) on tag objects to provide user-friendly display names in navigation and landing pages while maintaining stable URLs based on the canonical tag name.
123
123
124
124
```json
125
125
{
@@ -139,7 +139,35 @@ Use the `x-displayName` extension on tag objects to provide user-friendly displa
139
139
```
140
140
141
141
**Behavior:**
142
+
142
143
- When `x-displayName` is present, it's used for navigation titles and section headings in the API Explorer
143
144
- When `x-displayName` is absent, the canonical tag `name` is used as a fallback
144
145
- Navigation URLs and internal references always use the canonical tag `name` for stability
145
-
- This extension follows the [Redocly specification extension pattern](https://redocly.com/docs-legacy/api-reference-docs/specification-extensions/x-display-name)
146
+
147
+
### `x-tagGroups` for sidebar grouping
148
+
149
+
Use the document-level `x-tagGroups` extension (from [Redocly](https://redocly.com/docs-legacy/api-reference-docs/specification-extensions/x-tag-groups)) to define how tags are grouped in the API Explorer sidebar. Each group has a display `name` and a list of tag `name` values that belong to it. Group order in the array is the order of top-level sections in the navigation.
- When `x-tagGroups` is present and valid, the API Explorer uses it as an additional level of grouping in the sidebar.
172
+
- When `x-tagGroups` is absent, tags are listed directly under the API root in a single flat layer.
173
+
- Any operation tag that is not listed under any group is still included: it appears under a fallback section named `unknown`, and the build logs a warning so you can fix the spec.
0 commit comments