TATSUNO “Taz” Yasuhiro

Results 152 comments of TATSUNO “Taz” Yasuhiro

This issues can be reproduced with v0.8.0, but v0.9.0 and above is fine. Please use newer version

Right now, this is not doable. rspec-openapi preserves most of manually added fields (`additionalProperties` for this case) but resurrect `properties`. We may omit `properties` if there is already `additionalProperties` manually...

Implemented in https://github.com/exoego/rspec-openapi/pull/178

Interesting. I did not know `examples` that can contain multiple examples https://swagger.io/docs/specification/adding-examples/ I am happy to accept pull request. I prefer it defaults to single `example` and add a feature...

> Let me know if there are any workarounds or if you think this might be a quick fix. [Test cases can be excluded from OpenAPI generation with `openapi: false`...

@blocknotes Sorry for late response. Adding example like this sounds great to me. PR welcome.

I think this is a bit controversial change. https://swagger.io/docs/specification/data-models/data-types/#readonly-write-only > `readOnly` properties are included in responses but not in requests, and `writeOnly` properties may be sent in requests but not...

This automatic deletion is a new behavior introduced in v0.7.0. In the previous versions, to delete the non-existent endpoints/parameters/fields in a request or response, users needed to delete the OpenAPI...