<p dir="auto">This is not a bug request, but rather, it's a discussion on the reasons why you named 2 prop types of <code class="notranslate">TextField</code> almost the same with one being upper case.<br>
According to <a href="https://material-ui-next.com/api/text-field/#textfield" rel="nofollow">TextField API</a>,<br>
<code class="notranslate">TextField</code> exposes two prop types  with almost same names. <code class="notranslate">InputProps</code> and <code class="notranslate">inputProps</code>.<br>
Currently, my Eslint gives me an error for having duplicate prop type.<br>
Is there any reason to name 2 prop types almost the same?<br>
Can't we rename 1 of them to something more clarifying?<br>
This also gives headaches with linting tools.</p>
<h2 dir="auto">Expected Behavior</h2>
<p dir="auto">Eslint or any other linting tool doesn't give me any duplicate error.(<code class="notranslate">react/jsx-no-duplicate-props</code>).</p>
<h2 dir="auto">Current Behavior</h2>
<p dir="auto">Eslint throwing duplicate prop error.</p>
<p dir="auto">Plugin is located <a href="https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/jsx-no-duplicate-props.md">here</a>.</p>
<p dir="auto">##Temporal solution<br>
Yes, you can set <code class="notranslate">ignoreCase</code> to false in <code class="notranslate">.eslintrc</code> but isn't it better to name our props in a more definitive way?<br>
Thank you.</p>
<h2 dir="auto">Your Environment</h2>

<table role="table">
<thead>
<tr>
<th>Tech</th>
<th>Version</th>
</tr>
</thead>
<tbody>
<tr>
<td>Material-UI</td>
<td>1.0.0-beta30</td>
</tr>
<tr>
<td>React</td>
<td>^16.0.0</td>
</tr>
<tr>
<td>eslint</td>
<td>^4.8.0</td>
</tr>
</tbody>
</table>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the <a href="https://github.com/callemall/material-ui/issues">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<p dir="auto">I was thinking I could contribute a "solo field" to Material UI, if you're interested, and given you don't already have a solution for it already. The idea is to have a input field that can be used as the main search form in webapps. I have created a custom one that I use together with material-ui, and figured it would be cool to make a contribution to the project.</p>
<p dir="auto">First of all, does it make sense to have this as a component or is the idea that it is easy enough to change the existing TextField / AutoComplete components with the new <code class="notranslate">classes</code> API and <code class="notranslate">withStyles</code> HOC?</p>
<p dir="auto">Second, I was thinking of making it a separate component, but perhaps it's better to include it in the existing TextField component? Thoughts? Actually, when I think about it, it definitely needs to support auto-complete, so on a second thought it should probably rely on AutoComplete (which I assume in turn is based on TextField).</p>
<p dir="auto">It should support an icon (and potentially a drop down menu) and auto-complete.</p>
<p dir="auto">Examples:</p>
<ul dir="auto">
<li>Search for "solo fields" in the <a href="https://material.io/guidelines/components/text-fields.html#text-fields-field-variations" rel="nofollow">Text fields spec</a></li>
<li>Search for "Floating toolbar" in the <a href="https://material.io/guidelines/layout/structure.html#structure-toolbars" rel="nofollow">Layout/structure guideline</a></li>
<li><a href="https://www.google.com/maps/" rel="nofollow">Google Maps</a> - floating toolbar with solo field</li>
<li><a href="https://drive.google.com/drive/my-drive" rel="nofollow">Google Drive</a> - the search field in the toolbar</li>
</ul>
<p dir="auto">Screenshot examples:</p>
<p dir="auto">Floating toolbar with solo field:<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/2538130/30308290-38b91576-9739-11e7-8b01-3cf9ce37f24f.png"><img src="https://user-images.githubusercontent.com/2538130/30308290-38b91576-9739-11e7-8b01-3cf9ce37f24f.png" alt="image" style="max-width: 100%;"></a></p>
<p dir="auto">Regular toolbar/app bar with solo field:<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/2538130/30308350-991b0d2a-9739-11e7-9494-b3aad78f4cf5.png"><img src="https://user-images.githubusercontent.com/2538130/30308350-991b0d2a-9739-11e7-9494-b3aad78f4cf5.png" alt="image" style="max-width: 100%;"></a></p>