OpenAPI 3.0.0

[daurnimator]

https://www.openapis.org/blog/2017/07/26/the-oai-announces-the-openapi-specification-3-0-0
https://blog.readme.io/an-example-filled-guide-to-swagger-3-2/

See also GetShopTV/swagger2#105

[larsnaesbye]

OpenAPI 3 would be real useful indeed, as it is often required.

[daurnimator]

often required by whom?

[larsnaesbye]

Well, by people who write requirements specifications :-D

[kosmonaffft]

There are any progress in implementing of OpenAPI 3.0 specifications?

[kljensen]

OpenAPI 3.0 supports Bearer authentication in a way that v2 does not. It would be nice for Postgrest to generate (or support) v3 OpenAPI responses for those of us using Swagger-ui or similar tools.

[yasz]

can it support now?

[tonyxiao]

Potential workaround for those interested is proxying postgREST root response and use something like https://github.com/Mermade/oas-kit/blob/main/packages/swagger2openapi/README.md to dynamically convert to v3 spec. On top of that it allows you to customize the oas document.

[DaemonAlchemist]

This would be very useful, as it appears that ChatGPT requires OpenAPI 3.0 specs for its plugins and custom actions.

[Garett-MacGowan]

This would be very useful, as it appears that ChatGPT requires OpenAPI 3.0 specs for its plugins and custom actions.

+1

[Garett-MacGowan]

I found the official spec converter here: https://github.com/swagger-api/swagger-converter/blob/master/src/main/swagger/swagger.yaml

It's provided as a docker container, so I'm going to go with the proxy approach as suggested by @tonyxiao

[steve-chavez]

FYI, there's work in progress for OpenAPI 3 on https://github.com/PostgREST/postgrest-openapi/