OpenAPI-Specification
OpenAPI-Specification copied to clipboard
OAI
The OpenAPI Specification Repository
I have been trying to use Open API to specify the expected Cache rules for some API routes While defining such rules through the `Expires` and/or `Pragma` headers can be...
The spec forbids the use of $refs to define entries in the `servers` array. The unfortunate result of this is duplication of information in several specification files, even though the...
Hello, it would be great for reusability if I could overwrite the `required` field of parameter and header objects, like I can overwrite`summary` and `description` in OpenAPI 3.1. ```yaml paths:...
I suggest that we add "default responses" that can be defined as default response for All endpoints. This would avoid copy-paste for some common responses like: 429 Too Many Requests...
I have Controller with multiple GET endpoints having same path. The only difference is the `@RequestParam `passed into the method. This is perfectly valid and common scenario in APIs. Spring...
gh pr checkout 2661 _Originally posted by @tg-bot-ap in https://github.com/OAI/OpenAPI-Specification/pull/2661#pullrequestreview-1019539810_
In my request model, I have a field like @NotNull @Schema(example = "19680228", type = "String", format = "yyyyMMdd", pattern = "([0-9]{4})(?:[0-9]{2})([0-9]{2})", required = true, nullable = false) @JsonDeserialize(using =...
## I expect - a Security Consideration section / document ## Instead - there is not - some security hints are scattered throughout the document See https://github.com/ietf-wg-httpapi/mediatypes/pull/49/files#diff-b22c3a369e1499074590046ad01b71334e21c491c64ccf045f8858e2d3036e56R543 cc: @darrelmiller
