Allow only pulling in specific builtins about tera HOT 4 CLOSED

The way it's going to work for v2 is that you will have some built-in filters/fn/tests that don't require deps directly in Tera. Anything else will be a in a tera-contrib package with individual features for each element

from tera.

Would I be able to make a PR for v1 while v2 is still a work in progress? Or do you think v2 is stable enough to make the switch already?

My plan is to decrease the amount of dependencies Bevy uses in its CI, with Tera being the first on the list. The only filter it needs is slugify. The templates are relatively simple.

from tera.

v2 is not coming that soon. For your usecase you can just disable the built-in feature and copy paste the slugify filter?

from tera.

To be honest I didn't realize you can register your own filters. Thanks for the idea!

Have a good weekend

from tera.