Status and support

No files, tests, or code entry points are named. Read the issue and its three-comment thread first, then review the repository's current activity and support situation; this is done only when maintainers decide whether and how to grow the core developer team.

Hi @p1c2u,

First of all, I’d like to express my appreciation for this library and the work you and the community have invested so far. IMHO, this is conceptually the best approach to leveraging OpenAPI server-side, i.e. implementing request/response validation and unmarshaling completely independent of a particular web framework, which makes it reusable, and offering adapters and extensions/middlewares for some popular web frameworks. This is a beautiful separation of concerns which many other projects are lacking. If it was up to me, all other OpenAPI server related projects should build on openapi-core (and your related projects) and not reinvent the wheel over and over. One of those projects I mean is Connexion which, as far as I can tell, is the most feature-rich OpenAPI-first solution for Python at the moment and quite popular. But it’s a monolith with regard to its OpenAPI-related code, so that community is maintaining a non-reusable implementation just for this one project. And with newer releases of the OpenAPI spec, e.g. v3.1, all those projects will take a long time for adding support because forces are not joined.

I think openapi-core should be the common foundation like, e.g., jsonschema is pretty much used everywhere where JSON Schema validation is needed. But for this to become a reality, I believe openapi-core needs to mature a bit more, add some missing features, become more reliable in terms of activity and community management, and then a ton of communications work will be needed for convincing projects like Connexion to adopt it and drop their own implementation. I imagine this is just a side-project for you and you’re managing it in the best way possible, time allowing, that’s why I’m wondering whether you’ve been considering to grow the core developer team.

I fully believe in the value and the benefits of OpenAPI, and that’s why I’m generally puzzled why the OpenAPI-related tooling across numerous popular programming languages is in such bad shape. I’d love to see it improve, particularly for Python, and that’s why I’m reaching out. 🙂