Add an easy API in the templates to add a class to an input element.

[gregmuellegger]

This issue was brought up recently by #86 and is quite a basic use case. So we need to come up with:

• an API how to add classes to form widgets.

[benoitbryon]

A naive implementation could use {{ extra_classes }} context data in templates/floppyforms/attrs.html. Something like that:

{{ name }}{% if value|stringformat:"s" != "True" or value != 1 %}="{{ value }}{% if name == "class" %} {{ extra_classes }}{% endif %}"

Then what about {% widget %} accepting options such as using and with? It would make it easy to provide custom context data and to use alternative templates for widgets.

Another option would be to update field's attrs dictionary (or a copy of it)... but, right now, I do not have a nice idea about how to do it in a simple an safe way.

[treyhunner]

You could implement this similarly to the rend_field tag or add_class filter in django-widget-tweaks.

[eagle-r]

Is there anything happening on this issue in the near future or is there a recommended workaround?

Our project calls for Bootstrap3 and we're running into this very issue. I've looked at #86 and unfortunately https://github.com/grundleborg/django-floppyforms-bootstrap3 is only a partial implementation.

I tried creating a Bootstrap layout based on the one in the docs with a modified version of attrs.html but my layout doesn't seem to be ignoring that template for some reason. Is there a formconfig that I need to use to get it to reference my attrs.html rather than the standard one?

I've also tried adding the CSS class via the with option for the formfield tag but that doesn't seem to be passed through either.

Any other suggestions? Thanks.