Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flask blueprint naming clash #31

Open
elmanm opened this issue Nov 8, 2021 · 1 comment
Open

flask blueprint naming clash #31

elmanm opened this issue Nov 8, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@elmanm
Copy link

elmanm commented Nov 8, 2021

I haven't tested this with other handler integrations but in the flask integration, because the Blueprint is created with a hardcoded name "swagger_blueprint", you can't add ui more than once (e.g. if you have have multiple specifications for different versions), because each Blueprint must have a unique name.

It would be nice if the name was derived from the ApplicationDocument.title or ApplicationDocument.url_prefix, so it can be set per document if needed.

@PWZER PWZER added the bug Something isn't working label Nov 29, 2021
@PWZER
Copy link
Owner

PWZER commented Nov 29, 2021

There could be a problem,thank you for your advice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants