You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of the noDuplicateJsxProps rule is case-sensitive but JSX handles props in a case-insensitive manner so 2 props with the same name but different cases are treated separately and are valid.
A good example of this is the MUI TextField component which has inputProps and InputProps props which when used cause the Biome lint command to fail.
Note that this bug isn't about the semantics of whether or not using 2 props with the same name is good practice or not (IMO it's bad practice).
Expected result
The noDuplicateJsxProps rule should be case-sensitive.
Code of Conduct
I agree to follow Biome's Code of Conduct
The text was updated successfully, but these errors were encountered:
Environment information
What happened?
The current implementation of the
noDuplicateJsxProps
rule is case-sensitive but JSX handles props in a case-insensitive manner so 2 props with the same name but different cases are treated separately and are valid.A good example of this is the MUI TextField component which has
inputProps
andInputProps
props which when used cause the Biomelint
command to fail.Note that this bug isn't about the semantics of whether or not using 2 props with the same name is good practice or not (IMO it's bad practice).
Expected result
The
noDuplicateJsxProps
rule should be case-sensitive.Code of Conduct
The text was updated successfully, but these errors were encountered: