Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Actually use the Jinja2 template backend #1882

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from
Draft

Actually use the Jinja2 template backend #1882

wants to merge 4 commits into from
+69 −5

Commits on Feb 12, 2024

  1. Actually use the Jinja2 template backend 

    Refs #1881.
    @matthiask
    matthiask committed Feb 12, 2024
    Configuration menu
    Copy the full SHA
    8022782 View commit details
    Browse the repository at this point in the history

Commits on Feb 18, 2024

  1. Add jinja2 template to example app.

    @tim-schilling
    tim-schilling committed Feb 18, 2024
    Configuration menu
    Copy the full SHA
    d49a2d0 View commit details
    Browse the repository at this point in the history

Commits on Feb 19, 2024

  1. Switch to the render function so we can include context.

    @tim-schilling
    tim-schilling committed Feb 19, 2024
    Configuration menu
    Copy the full SHA
    39e2e77 View commit details
    Browse the repository at this point in the history

  2. WIP: instrument the jinja render function (more) 

    It instruments the single template render, but not the inherited
templates and I'm guessing not the included templates either.
I suspect we're going to have to patch jinja templates more robustly
than relying on the django jinja backend template class.
    @tim-schilling
    tim-schilling committed Feb 19, 2024
    Configuration menu
    Copy the full SHA
    8db3450 View commit details
    Browse the repository at this point in the history