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
I am using this plugin with React and Typescript and I have found it very useful so far.
However, I think it would be useful to add an ignoreAttribute option, similar to ignoreCallee but for JSX attributes.
In the example above variant and margin are not reported as errors because their types are defined as a an union type of different strings.
But name and autocomplete are of type string so they get reported.
An ignoreAttribute option is necessary because the other solution would be spamming every file with eslint-disable-next-line comments.
And adding other attributes to the whitelist (like has been done with #4) for every framework and library that comes along would just be unfeasible.
I could work on the PR myself, just need to know if you would merge it.
The text was updated successfully, but these errors were encountered:
I am using this plugin with React and Typescript and I have found it very useful so far.
However, I think it would be useful to add an
ignoreAttribute
option, similar toignoreCallee
but for JSX attributes.The reason is:
In the example above
variant
andmargin
are not reported as errors because their types are defined as a an union type of different strings.But
name
andautocomplete
are of typestring
so they get reported.An
ignoreAttribute
option is necessary because the other solution would be spamming every file witheslint-disable-next-line
comments.And adding other attributes to the whitelist (like has been done with #4) for every framework and library that comes along would just be unfeasible.
I could work on the PR myself, just need to know if you would merge it.
The text was updated successfully, but these errors were encountered: