OpenAPI3 support

[esseti]

As per this issue in the father project, is anything planned to finally support OpenAPI3 standards in this package?

https://github.com/axnsan12/drf-yasg/issues/33

[johnthagen]

It's worth mentioning that drf-spectacular exists to support this exact use case. I haven't used it personally, but from the DRF docs:

drf-spectacular is a OpenAPI 3 schema generation tool with explicit focus on extensibility, customizability and client generation. It's usage patterns are very similar to drf-yasg.

[tfranzel]

@johnthagen thanks for mentioning it. we exclusively do OpenAPI 3. initially, we also used yasg and thus tried staying close to yasg in terms of look and feel. some things are nearly the same, other deviate considerably. worth noting that the underlying implementation is not based on yasg, as it was initially planned to be upstreamed into DRF (which didn't pan out).

anyways, kind of sad that Christi disappeared. big thumbs up to @JoelLefkowitz for picking up yasg and maintaining it. it's still an awesome lib.

[JoelLefkowitz]

@johnthagen thanks for mentioning it. we exclusively do OpenAPI 3. initially, we also used yasg and thus tried staying close to yasg in terms of look and feel. some things are nearly the same, other deviate considerably. worth noting that the underlying implementation is not based on yasg, as it was initially planned to be upstreamed into DRF (which didn't pan out).

anyways, kind of sad that Christi disappeared. big thumbs up to @JoelLefkowitz for picking up yasg and maintaining it. it's still an awesome lib.

Cristsi is back and we're working on the original repo again. It is worthwhile continuing to track this issue there axnsan12#33