Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
On using the is-valid bootstrap4 class or not
See original GitHub issue- Package version: github head
- Django version: 2.1
- Python version: 3.6.7
- Template pack: (Optional) bootstrap4
Description:
Boostrap 4 allows to display even more explicitly which field validate or not after server-side validation as you can see in the documentation
Correct me if I am wrong, but we know that a forms.Form has received data when is_bound is True.
We would thus need to render the field with is-valid or is-invalid depending on the presense of field.erros, but only if the form is_bound.
For now I don’t know how to get this information when rendering the field, so my question is twofold:
- Can we access the form object when rendering a field ?
- Is it worth it to use is-valid ?
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ok, I see. I don’t think that django-filter should suggest any different than what it is doing now as the GET dict is always there. This digs one of my first question which was “Is it worth it to use is-valid ?”. Considering that is-valid will be rendered for every from with GET data, I think we should consider removing the is-valid, and only keep the is-invalid. Would it be ok with you @carltongibson @eriktelepovsky ?
Yes, I think it is the correct approach. Thanks guys.