-
-
Notifications
You must be signed in to change notification settings - Fork 16.3k
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
use blueprint specified template folder #1537
Conversation
|
||
if request.blueprint is not None and \ | ||
isinstance(template_name_or_list, string_types): | ||
bp = current_app.blueprints[request.blueprint] |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Unless I am greatly mistaken this will break anyone out there who is using extensions and overriding (not inheriting from) the extension's blueprints. For example, given the following extension setup:
before this patch, overriding
And making sure that With this patch, I don't think there is a way to override |
Agree with @svieira, this is the point I was making in my comment on the original issue.
|
Those commits should be squashed into a single one eventually. Also, this would be a breaking change depending on the application structure, so I'd rather make it configurable, with the current behavior being the default. |
If configurable it would have to be done at the I created #1548 to talk about some another possibility that might solve several of these issues in one go. |
Is there any update on when this fix could be merged or implemented in a different manner? |
The referenced issue was closed as wontfix. |
Fixes issue #1361.