Implement the x-tags
extension for schema objects
#837
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.
Description
This change enables schemas to have
x-tags
defined for them, which allows them to be grouped alongside related path objects whensidebarOptions.groupPathsBy: 'tag'
is configured.Motivation and Context
In reporting the unexpected behavior in #836, I began poking around and discovered the
x-tags
extension by redocly. It seems like a useful feature, and was easy enough to get working.It's intended (by redocly, and so here) that it's a "competing" option for configuring
showSchemas: true
, which is why you'll see some changes to the checks/logic inopenapi/openapi.ts
surrounding if/when to add schema objects to the sidebar slice.How Has This Been Tested?
Tested this on my local computer, using the demo app. I've added (only locally, I think)
x-tags
to a few of the defined schemas, and made sure they show up where they belong.Screenshots (if appropriate)
Types of changes
Checklist