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
|`categoryLinkSource`|`string`|`null`| Defines what source to use for rendering category link pages when grouping paths by tag. <br/><br/>The supported options are as follows: <br/><br/> `tag`: Sets the category link config type to `generated-index` and uses the tag description as the link config description. <br/><br/>`info`: Sets the category link config type to `doc` and renders the `info` section as the category link (recommended only for multi/micro-spec scenarios). <br/><br/>`none`: Does not create pages for categories, only groups that can be expanded/collapsed. |
Describe the problem
The documentation indicates categoryLinkSource supports a none option, however, the plugin only accepts [tag, info, auto]
[ValidationError]: "config.api.sidebarOptions.categoryLinkSource" must be one of [tag, info, auto]
Suggested fix
Can we confirm if this functionality is no longer supported, and if so, remove this from the documentation?
If this option is no longer available, I would love to see this as a feature request. I am trying to remove category index page links from my sidebar and this would have been a huge help.
The text was updated successfully, but these errors were encountered:
Documentation link
docusaurus-openapi-docs/README.md
Line 180 in db293ef
Describe the problem
The documentation indicates
categoryLinkSource
supports anone
option, however, the plugin only accepts[tag, info, auto]
[ValidationError]: "config.api.sidebarOptions.categoryLinkSource" must be one of [tag, info, auto]
Suggested fix
Can we confirm if this functionality is no longer supported, and if so, remove this from the documentation?
If this option is no longer available, I would love to see this as a feature request. I am trying to remove category index page links from my sidebar and this would have been a huge help.
The text was updated successfully, but these errors were encountered: