Francois LASNE
Francois LASNE
- 3.2 / 3.1 ? / 3.0 https://github.com/OAI/OpenAPI-Specification/issues/3934
@handrews looks fair request , that can be handle in moonwalk or in a 3.2 version , or close forever :) as as there are work around leveraging server variables...
i understand the purpose & value of those 2 fields dataValue vs serializedValue but i would rather **add a single one**, keeping current value , and clearly document that it...
for the actual field : we have in fact 4 choices 1. actual description followed is only by a few number and will break the majority 2. change de description,...
hello @nissimsan in your OAS you can defines that you are using Oauth2 , client credential flow exactly as your are doing in your spec ``` securitySchemes: OAuth2: type: oauth2...
given https://spec.openapis.org/oas/latest.html#optional-oauth2-security , there is a sample mentionning "Optional OAuth2 security as would be defined " with the sample `{ "security": [ {}, { "petstore_auth": [ "write:pets", "read:pets" ] }...
You are right as of today there is no way no manipulate the content disposition , this would be something to add in OAS 3.2 or 3.+ adding RFC link...
a way to support Idempotency is to follow this https://datatracker.ietf.org/doc/draft-ietf-httpapi-idempotency-key-header/ but it is more on the how to implement not about setting a description , as it can be implemented...
closing the ticket , as it is an implementation pattern rather than a being in OAS scope