Recently we have been using add_prefix() function on form objects to push Django to render field's name (and other identifiers) with a specific prefix in it. We found out that the Django-Angular was rendering properly everything except the errors coming directly from Django (custom errors added on our clean() methods inside forms).
We have seen that the prefixed field's name is only available in html_name not in name, which keeps the form's original name. To make Django-Angular to render this last
properly, we have changed field.name with field.html_name.
So far we haven't found any incompatibility on the demo site.
jrief
commented
9 years ago
Recently we have been using add_prefix() function on form objects to push Django to render field's name (and other identifiers) with a specific prefix in it. We found out that the Django-Angular was rendering properly everything except the errors coming directly from Django (custom errors added on our clean() methods inside forms).
We have seen that the prefixed field's name is only available in html_name not in name, which keeps the form's original name. To make Django-Angular to render this last
properly, we have changed field.name with field.html_name.
So far we haven't found any incompatibility on the demo site.