openapi_parser
openapi_parser copied to clipboard
ota42y
validate and coerce parameter using OpenAPI3 definition
### Description For now, when passing schemas like : ```yml type: object required: - head_count properties: head_count: type: integer format: int64 mass: type: integer additionalProperties: type: string ``` there is...
### Description OpenAPI supports exploded array parameters, such as `stuff[]=foo&stuff[]=bar`. However, when operating in a Rails environment (or any other server environment which parses these exploded parameters into a single...
# Proposal - The library type should read and use gem_rbs_collection. - Methods whose types do not match are overloaded. If the gem_rbs_collection type is sufficient, the handwritten type definitions...
OpenAPI 3 support `require` id header but openapi_parser not support yet :(
Now that we support Ruby 2.7 and above, we can remove conditions with versions lower than that.
Hi, first of all, thanks for all your efforts on this project! I noticed that string validation for the uuid format is a bit too lax and passes on obviously...
## Description OpenAPI supports multiple methods of parameter deserialization. Documentation here: https://swagger.io/docs/specification/serialization/ In order to parse these comma-separated, pipe-delimited, and space-delimited arrays, we need to deserialize them according to the...
Hi,team👋 Only the test was described for now. Because it could be a major structural reform, I would like to discuss whether I should fix the implementation before proceeding. Closes：https://github.com/ota42y/openapi_parser/issues/156
## Failure that occurred Validation fails when using `oneOf` and `properties` in parallel. ``` one_of_alongside_properties: additionalProperties: false required: - shared_property properties: shared_property: type: string oneOf: - $ref: '#/components/schemas/one_of_object1' - $ref:...