If this was to be an addition to 'include' it would result in it having an optional closing tag, that seems a little confusing and you would need an argument to flag that there are blocks to override (and parse until the 'endinclude').
The advantage over Jonathans 'decorate' tag is that you can override any and multiple blocks in the included template. On Wednesday, September 3, 2014 5:46:24 PM UTC+1, Jonathan Slenders wrote: > > From 2011: > https://github.com/vikingco/django-template-tags/blob/master/src/django_template_tags/templatetags/decorate.py > > My proposal was refused back then, but I'll be very happy if something > similar would make it. :) > > > > Le mercredi 3 septembre 2014 18:42:44 UTC+2, Jonathan Slenders a écrit : >> >> It's not similar. This implements the "decorator" pattern. Something that >> I've been proposing years ago. >> >> >> >> Le mercredi 3 septembre 2014 18:24:17 UTC+2, Ian a écrit : >>> >>> On Wed, Sep 3, 2014 at 10:10 AM, Sam Willis <[email protected]> wrote: >>> > Although I have implemented this with the 'use' word, there may be a >>> better >>> > word. I considered 'embed' but thought 'use' was a little cleaner >>> >>> Since it's so similar to 'include', is there a reason not to just add >>> the new functionality to the existing tag? >>> >> -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5380864a-642d-44f6-bd58-31c555a517a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
