frontend: migrate all templates to Jinja2 #377
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All templates (web, email, txt) were migrated to Jinja2, except those in
'squad/templates/django' due to lack of support of Django Rest Framework
along with Jinja. Bellow are a few items worth mentioning:
using Jinja2's syntax
and filters, following Jinja2 guidelines
from Django and load squad's custom templatetags
unchanged since Django Rest Framework does NOT support
jinja2, nor it's going to be supporting (didn't see any)
issue addressing that on their repo to date
fail silently (tag 'with') whereas jinja doesn't. Found several
templates that were crashing after migrated to Jinja