Eslint giving error for duplicate props

[mehrdad-shokri]

This is not a bug request, but rather, it's a discussion on the reasons why you named 2 prop types of TextField almost the same with one being upper case.
According to TextField API,
TextField exposes two prop types with almost same names. InputProps and inputProps.
Currently, my Eslint gives me an error for having duplicate prop type.
Is there any reason to name 2 prop types almost the same?
Can't we rename 1 of them to something more clarifying?
This also gives headaches with linting tools.

Expected Behavior

Eslint or any other linting tool doesn't give me any duplicate error.(react/jsx-no-duplicate-props).

Current Behavior

Eslint throwing duplicate prop error.

Plugin is located here.

##Temporal solution
Yes, you can set ignoreCase to false in .eslintrc but isn't it better to name our props in a more definitive way?
Thank you.

Your Environment

Tech	Version
Material-UI	1.0.0-beta30
React	^16.0.0
eslint	^4.8.0

[mehrdad-shokri]

Also, please note that Airbnb eslint style uses jsx-no-duplicate with ignore case of true.

[oliviertassinari]

please note that Airbnb eslint style uses jsx-no-duplicate with ignore case of true.

@mehrdaad This is key to the issue. https://github.com/airbnb/javascript/blob/53b2d7d245ba4abefc0429bfda4a46f099b9ace5/packages/eslint-config-airbnb/rules/react.js#L89

Can't we rename 1 of them to something more clarifying?

Input refers to the Input component when input refers to the input element.

[mehrdad-shokri]

Input refers to the Input component when input refers to the input element.

I've already read that in docs.

What I'm suggesting is rename one of the prop types for more clarification.

and also not getting an error from Airbnb style eslint rules.

[oliviertassinari]

@mehrdaad I have added the waiting for users upvotes tag. I'm closing the issue as it unsure if changing the property names will make the situation better. So please upvote this issue if you think it would. Suggestions are even better! We will prioritize our effort based on the number of upvotes.
You can suppress this eslint warning for now.

[oliviertassinari]

I have found the following solution to the problem: much cleaner:

<TextField
- inputProps={{
-   foo: true
- }}
  InputProps={{
    bar: true,
+   inputProps: {
+     foo: true,
+   },
  }}

[vaibhavhrt]

Add this to your .eslintrc.json

{
    ...
    "rules": {
        ...
        "react/jsx-no-duplicate-props": [1, { "ignoreCase": false }]
        ...
    },
    ...
}

This will warn when there are two props of same name. Use 2 instead of 1 for error.

[nghtstr]

I think an even better solution is to have InputProps do as what is expected, but change inputProps to NativeInputProps. That is far more descriptive as to what it does. Having it as the same name, but differing only by the case of the property is prone to errors and simple typos. Changing the native element props to NativeInputProps keeps with the standard of having the properties staring with an upper case as well as makes it far more descriptive.