Hi Florian, thanks for your reply.
I clearly didn't express myself properly, so let me try again with a simple
example.
Suppose you are dealing with a detail view, whose context has an "object"
key that refers to the object being displayed. Then, in the rendered
template, you might have an inc
On Monday, September 15, 2014 3:24:19 PM UTC+2, germano guerrini wrote:
>
> I'd like to bump this. While there might be better solutions, I think the
> issue is not so wacky after all.
>
To be honest, I don't see an issue here at all. What the view returns
should end up in the template. If tags/
I'd like to bump this. While there might be better solutions, I think the
issue is not so wacky after all.
On Thursday, September 4, 2014 3:02:34 PM UTC+2, germano guerrini wrote:
>
> Hello everyone,
>
> while writing a test for a view, I found that one of the rendered
> templates context had a
Hello everyone,
while writing a test for a view, I found that one of the rendered templates
context had a key used by the main template of the view itself, but with a
different value.
Given the rendering order, calling
response.context[key]
would not return the view template context value, but
