Update extension.py to support Blueprint Name in init #167
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding APISPEC_BLUEPRINT_NAME, to prevent Error:
AssertionError: A name collision occurred between blueprints <flask.blueprints.Blueprint object at 0x11f474cc0> and <flask.blueprints.Blueprint object at 0x11ee7b898>. Both share the same name "flask-apispec". Blueprints that are created on the fly need unique names.
When trying to create 2 separate swagger endpoints for a set of resources. (i.e Public and Private)