@W-23748894 demo(webhooks): surface oas31-webhooks in the demo selector - #65
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.
What
Adds
oas31-webhooksto the api-documentation demo selector (demo/index.js) so the OAS 3.1 webhooks fixture is selectable from the demo dropdown.Why
#64 registered the
oas31-webhooksspec indemo/apis.jsonand shipped the per-operation Try-It suppression plus tests, but the demo's hardcoded selector list in_apiListTemplate()was never updated. The spec generates a model onnpm install, yet without a dropdown entry it isn't reachable from the running demo. This one-line follow-up surfaces it.Change
demo/index.js: add['oas31-webhooks', 'OAS 3.1 webhooks']to_apiListTemplate().Demo-only; no runtime/
srcchange.