Opened 8 years ago

Closed 8 years ago

#16305 closed New feature (wontfix)

Create a form.TextField() form field

Reported by: rich@… Owned by: nobody
Component: Forms Version: 1.3
Severity: Normal Keywords: forms, default
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no


To create a Text Field in a model, one calls:


yet to create a TextField in a form, one must:

forms.CharField(max_length=200, widget=forms.TextInput({}))

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?

Change History (2)

comment:1 Changed 8 years ago by anonymous

Sorry, all instance of TextInput above should read Textarea.

comment:2 Changed 8 years ago by Russell Keith-Magee

Resolution: wontfix
Status: newclosed

This suggestion misses the reason why the distinction exists in the first place. The form layer deals with data. The widget layer deals with presentation. The decision to use Textarea or a TextInput is purely presentational -- it has no effect on the data handling.

This is a situation where we'd gain a minor simplification for a limit set of use cases, in exchange for obscuring the distinction between the two layers. Marking wontfix for this reason.

Note: See TracTickets for help on using tickets.
Back to Top