What openapi features are unsupported?

[rtaycher]

I'm trying to generate a python library for an openapi definition.

I'm really tempted to use your generator over the official one (mainly because of type hints and dataclasses instead of dicts) but I'm not certain if that's a good idea since I don't know all of the ins-and-outs of openapi

The Readme lists 6 openapi features supported. But it seems to be a little out of date(it's been 9 months since the official generator released a version without python 2 support cruft)

But even if it wasn't out of date Im unaware of features I might need.

What are the major/commonly used
features of openapi that are not yet supported by openapi-python-client?

Is there any way to check the openapi file or the generated code to tell if my definition file is using something that is not supported/won't work (short of trying to execute each api)?

Is there any sort of roadmap for the remaining work outside of the issues listed?

P.S. regardless of whether I end up using it, thank you for writing the generator, it has a lot of cool stuff.

[dbanty]

If you run the generator on the spec it will produce a warning for most things unsupported. You're right that the claims and comparisons haven't been updated in a while, I just haven't gotten around to trying out the mainstream generator in a while.

I think the biggest things that aren't supported are circular schema references and remote references.

There is a GitHub issues project to which I try to add any feature requests for incomplete OpenAPI 3.0 functionality so that could be a place to look around if something seems off.

Generally speaking, all of the most standard / mainstream OpenAPI stuff is supported, it's just more complex, advanced, or poorly defined (there are a lot of those) specs that aren't included yet.