Jinja2 support plan

[thibaudcolas]

It would be nice for us to have a plan for this? We don’t use Jinja much at Torchbox, so we’d need someone to tell us what would be sensible for this package to do.

[easherma-truth]

We use Jinja for our site where I work, but I'm also coming from a similar boat as Torchbox. I'm not familiar enough with Jinja to say what it would take to make this library work with it.

[gone]

I've put a first pass at this in #206 - I'm motivated to get this merged in so any feedback would be appreciated!

I have a sample app up at https://github.com/gone/patternlib_jinja - if there's interest I can host a copy up on a service for people to poke at.
A couple points that are good to look at:

settings: https://github.com/gone/patternlib_jinja/blob/main/sampleapp/config/settings/base.py#L231-L249
pattern contexts that showcase global/template specific: https://github.com/gone/patternlib_jinja/blob/main/sampleapp/util/pattern_contexts.py

The samples I've been testing against:
A button - this showcases pulling in some data from yaml, from a global context and a pattern specific context
https://github.com/gone/patternlib_jinja/blob/main/sampleapp/templates/components/button.jinja

A extends/includes example
https://github.com/gone/patternlib_jinja/blob/main/sampleapp/templates/components/child.jinja

As I mentioned in the pr - if you target include_test or extends_test the context isn't included. Right now my thinking is that we can write some jinja extensions that target those tags, and then users will have to include those extensions into their jinja env config. I'm asking on discord if that's possible or for feedback on that approach.

[CuriousLearner]

Hi @gone We've fixed the branch with jinja support and it's here: gone#6

@thibaudcolas if you'd like we can open up this directly on the torchbox repo. Please let me know.

[zerolab]

@CuriousLearner please do

[CuriousLearner]

@zerolab Opened it here: #247