Create a form.TextField() form field
|Reported by:||rich@…||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
To create a Text Field in a model, one calls:
yet to create a TextField in a form, one must:
Also, a ModelForm can bind to a model with a TextField by creating a CharField with a TextInput widget, like above.
Why not make a forms.TextField as a shortcut (simply a CharField with a different default widget).
The key benefit here would simply to make the Forms and Models symmetrical. As a developer, using a TextField in one place and then a CharField/widgetTextInput in another place to create the same effect seems very counter-intuitive, especially when the fix is so simple.
What do you think?