Skip to content

fix: ignore non-apiKey security schemes in operation form - #61

Merged
BatLeDev merged 1 commit into
masterfrom
fix-non-apikey-security-schemes
Nov 9, 2026
Merged

BatLeDev merged 1 commit into
masterfrom
fix-non-apikey-security-schemes

Conversation

@BatLeDev

@BatLeDev BatLeDev commented Nov 9, 2026

Copy link
Copy Markdown
Member

Operations declaring an oauth2, http or openIdConnect security scheme crashed the operation page (Cannot read properties of undefined (reading 'properties')): the form builder indexed the form sections by the scheme's in, which only apiKey schemes have.

  • Only apiKey schemes located in header or query now produce a form field; other scheme types are skipped.
  • Parameters with an unknown location are skipped instead of crashing (previously only cookie and body were).
  • Every scheme of a combined security requirement ({ a: [], b: [] }) is resolved, not only the first one.
  • Unit tests cover getVJSFSchema for these cases.

Why: data-fair now declares an oauth2 scheme (NHI scopes) on its dataset operations, so opening any operation in the dataset API doc fails.

Operations declaring an oauth2 (or http / openIdConnect) security scheme
crashed the operation page: the form builder indexed schema.properties by
the scheme's `in`, which only apiKey schemes have. Only apiKey schemes in
header/query now produce a field, parameters with an unknown location are
skipped, and every scheme of a combined security requirement is resolved.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added the fix label Nov 9, 2026
@BatLeDev
BatLeDev merged commit 3856548 into master Nov 9, 2026
4 checks passed
@BatLeDev
BatLeDev deleted the fix-non-apikey-security-schemes branch November 9, 2026 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant