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
The Traits Example shows how to add query parameters for paging to an operation, which in this simple form would only work if the operation does not already have parameters.
How would this be extended to a less trivial case where operations may already have parameters?
openapi: 3.1.0info:
title: API with a paged collectionversion: 1.0.0paths:
/items:
get:
x-oai-traits: ['paged']responses:
200:
description: OK/items/{id}/subitems:
get:
x-oai-traits: ['paged']parameters:
- name: idin: pathrequired: trueresponses:
200:
description: OK
Would I have to specify an action for operation objects without parameters and actions for operation objects with parameters?
The Traits Example shows how to add query parameters for paging to an operation, which in this simple form would only work if the operation does not already have parameters.
How would this be extended to a less trivial case where operations may already have parameters?
Would I have to specify an action for operation objects without parameters and actions for operation objects with parameters?
The text was updated successfully, but these errors were encountered: