Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue in Client-Side Form Validation #325

Open
santhosh432 opened this issue Dec 1, 2017 · 3 comments
Open

Issue in Client-Side Form Validation #325

santhosh432 opened this issue Dec 1, 2017 · 3 comments

Comments

@santhosh432
Copy link

santhosh432 commented Dec 1, 2017

Hello jrief,
I have used the client side angular validations with boostarp3 and django1.11, the errors are displaying only if i coded with {{ form.as_div }} in the templates, but when i am using the {{ form.as_table }} the errors are not displaying.Please help me to resolve the issue

Thanks in advance....

@adrienbrunet
Copy link
Collaborator

Indeed, it is required to be used with as_div to work as expected.

@santhosh432
Copy link
Author

ok , is there any other possibilities to show the errors....
like {% for form in subform %}
{{ form.as_div }}
{% end for %}
I stuck with this issue....

@jrief
Copy link
Owner

jrief commented Dec 1, 2017

@santhosh432 here Django and Bootstrap have different opinions on how to represent form validation errors. If you can provide an example on how you would render a form using as_table in combination with BS3, that would be a good starting point.

Hint: Use the existing form rendered in the demo, transfer it to Plunker, Bootply, jsFiddle or whatever and change it accordingly.

Then for me it will be much easier to add that to the as_table() renderer.

@jrief jrief reopened this Dec 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants