-
Hey there,
thanks for your efforts maintaining and sharing this with us.
I'm currently attempting to migrate a huge codebase of Jinja2 compatible (Twig) templates to Minijinja, and macros seem to …
-
Replace current solution where global variables are inserted into template context with Environment.globals.
Similarly add option to define Template.globals from yaml.
https://jinja.palletsproject…
-
Today the engine holds `&'source str` all over the place in the instructions and by extension in the templates. This is a design pillar that I originally inherited from the initial API that was inspir…
-
The code would be more maintainable if we created a single `Context` object per set of language bindings instead of making a new ad-hoc object with `minijinja::context! {}` for each template. If we pu…
-
In essence, this feature would allow you to render _only_ a block from a template. This is great in the context of htmx where you typically want to just re-render a small section of html to send down …
-
## Description
If an empty line appears in a template on the line before a for/endfor block begins or on the last line of a for/endfor block, it will not appear in the rendered output.
However, …
-
I'm investigating how to migrate from `tera` to `minijinja`. https://github.com/zineland/zine/issues/109 However, `minijinja` lacks a good `Context` API like the `tera::Context` which my project relie…
-
A couple of times I have found myself wanting to use a JavaScript-like [optional chaining operator](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining) in Ji…
-
My use of Minijinja involves hooking a lot of complicated logic into the engine using custom functions and filters. This works *fantastically* well, apart from one small annoyance with error handling:…
-
Hello,
Currently, it's possible to create a source with a dynamic loader using `Source::with_loader` which accepts a callback function. That's really great but quite impractical to use in async cod…