simple include tag doesn't layer context like normal include tag
|Reported by:||Kenneth Arnold||Owned by:||nobody|
|Severity:||Normal||Keywords:||include custom tag library context layer inherit|
|Cc:||kenneth.arnold@…||Triage Stage:||Design decision needed|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
This was surprising behavior: unlike the provided include tag, user-defined include tags don't layer the provided context on top of the existing context.
It is consistent with a strict reading of the docs, but it's a confusing and un-motivated difference from ordinary include behavior.
I'm attaching a quick and dirty patch to fix this. The needed design decision is exactly how the context class should be handled; is there a use case for something other than just Context? (RequestContext needs another parameter...)
Change History (7)
comment:1 Changed 9 years ago by
|Patch needs improvement:||unset|
|Status:||new → closed|
comment:5 Changed 5 years ago by
|Status:||reopened → closed|