I prefer the first because it still follows the pattern of letting Django generate the form fields. But I think the second approach is just fine, and yeah you're right it's more obvious what's going on in the second.
hi thanks for this great video have a problem with date field, I need to show date field with custom format d-m-Y I did not see it in the documentation
short and well explained..thanks
Ty sooo much. Very useful and concise guide!
Ty bro, i relly needed this knowlege to make my project. Thanks!
thanks a lot, that was a life saver
Thanks for your knowledge, is it possible for you one day to cover about django crispy forms?
Straight to the point, thanks!
Thanks for watching!
Thank you so much for share!!!
Increible so good , thanks bro
Just wondering about error handling. Will the errors appear underneath the fields? Or is there a widget-tweaks thing for that?
Do you preffer this method of styling forms in django or maybe you more like creating normal html form with id="{{ form.x.id_for_label }}"?
In my opinion second method is better because it doesn't need any 3rd packages and it looks easier for juniors
I prefer the first because it still follows the pattern of letting Django generate the form fields. But I think the second approach is just fine, and yeah you're right it's more obvious what's going on in the second.
Thanks!
hi thanks for this great video have a problem with date field, I need to show date field with custom format d-m-Y I did not see it in the documentation
thanks ma dude
Can I use this line " class+=' ' " to add a class name and style it with CSS??
How can we show errors or add new errors with widget-tweaks?
It was useful