Description
I recently watched your 2016 DjangoCon video and really enjoyed your DynamicForm approach, and was thinking of implementing something similar for our website here at FluentCity. I know this repo is just a basic outline of what you use in production so before I go tumbling down the rabbit hole I was hoping I might trouble you with a few questions:
-
Do you have a recommended way of modifying the DynamicForm class to handle custom or non-Django 3rd party field types (e.g., 3rd party libraries like django-phoneumber-field).
-
In the production version of your code do you make use of any kind of single or multi-inheritance in your FieldContainer objects? I.e., does your FieldContainer or DynamicForm have the ability to inherit from and make use of fields on traditional Forms/ModelForms? (for example by plumbing into the
ModelForm.base_fields
attribute inside your DynamicForms__init__
method). -
Do you have any tips on the general structure your DynamicForm Validation API endpoint takes?