[TextField] Add inputProps back

[oliviertassinari]

Revert #9382 cc @rosskevin

As suggested by @kgregory how have been dealing with this recurring question on the discussion channels: #9575 (comment)

Providing extra properties to the native input is one of the top actions people are doing with the TextField component. We should make it as easy as possible.

[kgregory]

I approve, but think we should go further and eliminate all other props that pass through to the input element. Maybe another PR?

[oliviertassinari]

eliminate all other props that pass through to the input element

@kgregory Oh, you mean the name, value etc? Well, my understanding of the situation is that you will at have a:

• > 80% chance to use the bind properties (name, value, type, etc.)
• > 60% chance to need the inputProps property
• > 40% chance to need the XXXProps properties
• > 20% chance to have to use the lower level components

The less generic your use case is, the more painful it is to implement. It's all about the right tool for the right job.

[kgregory]

I was thinking of eliminating props that exist only so they can be passed to input, like autoComplete and autoFocus at this level, leaving them to InputProps (or inputProps if we eliminate them from Input as well). Props like name, value, and disabled make sense to keep.

[oliviertassinari]

@kgregory I have been adding those as people were requesting them. What sure is that we shouldn't add more. Now, regarding removing some. I have no certainty, maybe.
Personally, my strategy would be more: I would rather focus on other topics.
It's not like we have a lot right now:

    <Input
      autoComplete={autoComplete}
      autoFocus={autoFocus}
      defaultValue={defaultValue}
      disabled={disabled}
      multiline={multiline}
      name={name}
      rows={rows}
      rowsMax={rowsMax}
      type={type}
      value={value}
      id={id}
      inputRef={inputRef}
      onChange={onChange}
      placeholder={placeholder}
      {...InputProps}
    />

[kgregory]

@oliviertassinari that’s fine, I just felt as though supporting some input attributes would cause confusion. For example, autoFocus is supported, min and max are not. Maybe this can be handled in documentation. We draw a line at the attributes we’ve supported and push people toward inputProps for all others.