Solving Problems With Django Forms
summary
Describes concrete solutions: treat form fields as data and convert a field definition to a dictionary so an API can return a list of field names that get instantiated into self.fields at runtime; integrates third‑party validation by calling an API, mapping errors to fields and form.add_error integrates external errors so is_valid still works; supports user‑added fields via JavaScript with properly named inputs; warns crispyforms does not scale and reports success moving rendering to React + Redux with Django forms kept on the backend.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:10What are Django Forms?
- 2:48Dynamic Form Structure
- 6:50Rendering Dynamic Layouts
- 7:58Dynamic Form Validation
- 9:58User-Driven Fields
- 10:50Dynamic Fields
- 13:07Integration with ReactJS/Redux
related talks
27mGood form: How Django’s form rendering improved during the 4.x series
45mKeynote: All The Ways To Use Django with Zags
23mA different Form of navigation
27mBuilding a REST API with Django & Django REST Framework
25mWrite an API for Almost Anything (or The Amazing Power and Flexibility of Django Rest Framework)
46mCreating Solid APIs
01h 06mEffective Django
46mIntroducing Django REST framework