Why not just use {% include ... %} ?

Can you comment on why this is better than using {% include ... %}? https://jinja.palletsprojects.com/en/3.0.x/templates/#include

[carlbordum]

With jinja, I believe you can:

{% for v in videos %}
  <div class="video">
    {% with video=v email=user.email %}
      {% include "video.html"%}
    {% endwith %}
  </div>
{% endfor %}

[mikeckennedy]

Hi @nickleman

That will work I think. But it’s just more clumsy. Not too bad for one variable, the example we’ve been discussing needs two:

{% for v in videos %}

<div class="video">
      {% set email = user.email %}
      {% set video = v %}
      {% include "video.html" ignore missing with context %}
</div>

{% endfor %}

What if there is more?

{% for v in videos %}

<div class="video">
      {% set email = user.email %}
      {% set video = v %}
      {% set cat_name = category.category %}
      {% include "video.html" ignore missing with context %}
</div>

{% endfor %}

Does that still feel better than:

{% for v in videos %}

<div class="video">
    {{ render_partial("video.html", video=v, email=user.email, cat_name=category.category) }}
</div>

{% endfor %}

To me, definitely not. But if you don’t like how that looks, then go for the set multiple variables + include. It’s a choice for sure, not a requirement to use this library.