fix(theme): use matching auth scheme name in code snippet placeholders#1256
Merged
sserrata merged 1 commit intoPaloAltoNetworks:mainfrom Dec 17, 2025
Merged
Conversation
- Update the placeholder assignment logic to use find method for better accuracy. - Ensure the correct name is retrieved based on the key from authOptions.
|
Visit the preview URL for this PR (updated for commit 9364c8a): https://docusaurus-openapi-36b86--pr1256-25czq83b.web.app (expires Thu, 15 Jan 2026 22:19:13 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: bf293780ee827f578864d92193b8c2866acd459f |
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
2 participants
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
Changed
authOptions?.[0]?.nametoauthOptions?.find((opt: any) => opt.key === key)?.nameto find the correct auth scheme by key instead of always picking the first one.Motivation and Context
Fixes #1255
When an endpoint requires multiple auth schemes together (e.g. API Key + OAuth), the code snippet placeholder was always using the first scheme's name. This caused OAuth Bearer token to show
<X-API-Key>instead of the OAuth scheme's configured name.How Has This Been Tested?
Tested locally with an OpenAPI spec that has both
APIKeyandOAuthsecurity schemes required together on an endpoint. Verified the example now shows the correct placeholder for each scheme.Types of changes
Checklist