Support for "securityDefinitions" about flask-swagger HOT 3 OPEN

IMO, your current solution seems like the most reasonable way to accomplish this. Defining the base securityDefinitions inside of your docstrings does not fully make sense, as they should only be defined once at the base and then referenced inside your docstrings.

In that case, some clarification/examples in the docs might help. If this is insufficient for your needs, can you elaborate more on how you would like to see this working?

from flask-swagger.

The current solution is perfectly fine for me. But what I had in my mind, was to extract these securityDefinitions from the docstrings of any method to the top level, just like what is currently being done for definitions. Do you think this makes sense?

from flask-swagger.

Thanks @SandhyaGiri this definitely makes sense. I think I'm just trying to reason about conflict resolution in the event that there are two different security definitions with the same name. For example:

@app.route('/reports', methods=["POST"])
def sample_meth():
       """
       docstring
        ---
        securityDefinitions:
          ApiKeyAuth:
            type: apikey
            in: header
            name: X-API-Key

and then another view:

@app.route('/reports', methods=["POST"])
def sample_meth():
       """
       docstring
        ---
        securityDefinitions:
          ApiKeyAuth:
            type: apikey
            in: header
            name: X-API-Key-Different-Header

In this case, which definition would we expect to see in securityDefinitions? More importantly, which one would be used for the view?

The thing I like about your solution is that there is one and only one way to define the security definitions.

It looks like definitions gets handled by requiring an ID, so we could consider doing something similar with securityDefinitions if we want to.

from flask-swagger.