Escaping form html about jingo HOT 5 CLOSED

There is some code to monkeypatch safety in by default, like Django does for its template system. Maybe it makes sense to move this from nuggets to jingo itself?

from jingo.

Yes, martin if you move that code into jingo, I'll review it. WE should give enough batteries in jingo to make jinja usable in Django.

from jingo.

Thanks for patch, it`s actually working. But I not sure how this monkey patch works with classic django apps - imagine project using django templates in one app and jinja2 in second. Philosophically I tend towards to extend jinja2 to accept django.utils.safestring functions.

from jingo.

Going to finally take a look at this. safe_django_forms belongs in jingo.monkey or something similar.

from jingo.

I probably should've attached the PR in #26 to this instead, but oh well. Closing this in favor of the new one.

@martinsvoboda: Several of our projects are in the exact situation you described: the Django admin uses Django templates even with jingo/jinja2 installed. Adding __html__() to these form classes has no effect, because Django doesn't even know to look for it.

The only potential interference is from the change to conditional_escape, but it turns out it doesn't change much, or at least not for us. To be a little less intrusive, in #26 I changed the code from nuggets so that it respects both Jinja2 and Django's definition of "already safe".

from jingo.