You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 14, 2022. It is now read-only.
This may have been resolved unintentionally! Investigate before committing work.
What?
There's a couple of views in the WebApp that render other views inside them. This isn't great as the stack trace seems to be quite bad when something fails in the view that's being rendered inside the main view. DEBUG_PROPAGATE_EXCEPTIONS = True helps a bit, but the result is a huge traceback that's hard to read.
Where?
The two that come up with grepping {% view are:
Possible solution
I think a better approach is to include templates, but gather all the information in 1 view. We don't actually do LESS work when we split the view, we do just the same amount of querying anyway.
There's also some potential for reducing query duplication and optimising, as we can comprehend what's happening when it's in one place a lot better than when it's split into two, and we can share the objects.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue raised by: [developer/user/project requirement]
This may have been resolved unintentionally! Investigate before committing work.
What?
There's a couple of views in the WebApp that render other views inside them. This isn't great as the stack trace seems to be quite bad when something fails in the view that's being rendered inside the main view. DEBUG_PROPAGATE_EXCEPTIONS = True helps a bit, but the result is a huge traceback that's hard to read.
Where?
The two that come up with grepping
{% view
are:Possible solution
I think a better approach is to
include
templates, but gather all the information in 1 view. We don't actually do LESS work when we split the view, we do just the same amount of querying anyway.There's also some potential for reducing query duplication and optimising, as we can comprehend what's happening when it's in one place a lot better than when it's split into two, and we can share the objects.
The text was updated successfully, but these errors were encountered: