Feature request - Optiona to add top-level extensions to openapi spec about flask-openapi3

[luolingchun]

I will implement Specification Extensions in OpenAPI Object and Operation Object.

demo:

from flask_openapi3 import OpenAPI

openapi_extensions = {
    "x-google-endpoints": [
        {
            "name": "my-cool-api.endpoints.my-project-id.cloud.goog",
            "allowCors": True
        }
    ],
    "x-google-backend": {
        "address": "https://<NODE_SERVICE_ID>-<HASH>.a.run.app",
        "protocol": "h2"
    }
}

app = OpenAPI(__name__, openapi_extensions={"x-google-endpoints": openapi_extensions["x-google-endpoints"]})


@app.get("/books", openapi_extensions={"x-google-backend": openapi_extensions["x-google-backend"]})
def get_book():
    ...

[luolingchun]

I agree to add specification extensions support, but I think the conversion from OAS3 to OAS2 should be implemented by the user themselves.

Additionally, I believe that google cloud will support OAS3 in the future.

https://issuetracker.google.com/issues/78271318

There are many objects(like, OpenAPI, Components, Operation,Request Body, Responses, Schema, and more...) that support Specification Extensions, and I have no idea to implement those objects.

I noticed that FastAPI only implements Specification Extensions in Operation.

@simonblund I don't have any experience using Google Cloud. What do you want to implement about Specification Extensions?

[simonblund]

That looks awesome!! :D