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
This commit was created on GitHub.com and signed with GitHub’s verified signature.
@W-23748890 feat(query): add QUERY method color badge (OAS 3.2) (#100)
* feat(query): add QUERY method color badge (OAS 3.2)
OAS 3.2 introduces the QUERY HTTP method, which the archived
http-method-label package does not map, so QUERY operations rendered
in the default gray, indistinguishable from unmapped verbs.
Add a local color override for the QUERY method label. ApiUrl upper-cases
the method for display and lower-cases it for the color hook, so the badge
shows QUERY while data-method is 'query'; the rule keys on both casings.
Teal (#0f9d9d) is read-safe and does not collide with the PATCH purple.
W-23748890
* feat(oas32): add COPY and MOVE method-label colors
OAS 3.2 introduces the COPY and MOVE HTTP methods alongside QUERY. The
http-method-label palette has no entry for them, so they fall back to the
default gray. Add customizable color hooks matching the QUERY approach:
COPY renders indigo, MOVE renders amber. Both are exposed as CSS custom
properties (--http-method-label-copy/move-color and -background-color)
with sensible fallbacks, and both raw (uppercase) and lower-cased
data-method casings are keyed so navigation and documentation views agree.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* @W-23748890 test(query): drive QUERY label from generated OAS 3.2 model, bump generator to 0.4.0
Bump @api-components/api-model-generator ^0.2.14 -> ^0.4.0 (amf-client-js 5.11
supports OAS 3.1/3.2) and the amf-helper-mixin floor ^4.5.31 -> ^4.5.38. The
regenerated 5.11 models wrap custom domain extensions (the x-agent extension on
agents-api) in a single-element array; the agent resolver only navigates that
shape from 4.5.38+, where _computeNodeAgent uses _findCustomDomainPropertyByKey
instead of scanning for an inline amf://id# key.
Add a real OAS 3.2 demo spec exercising the QUERY method and register it so
prepare generates its model. Make test/amf-loader.js @graph-aware (amf-client-js
5.11 emits flattened @graph models; expand once at load time) and drive the
QUERY method-label test from the generated model instead of hand-building AMF.
COPY/MOVE stay inline with a comment: AMF 5.11 does not parse copy/move from an
OAS 3.2 pathItem.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* @W-23748890 demo(query): surface oas32-query in the demo selector
The QUERY method label (OAS 3.2) was registered in apis.json but not
reachable from the demo: the hardcoded selector list omitted the spec, so
the generated model never appeared in the dropdown. Add it as
'OAS 3.2 (QUERY)' so the QUERY badge can be previewed.
* @W-23748890 chore(release): bump version to 5.2.33
* @W-23748890 chore(deps): update package-lock.json for api-navigation 4.3.24 and amf-helper-mixin 4.5.38
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>