`no-unknown-property` doesn't prevent use of unknown properties?

[ryb73]

Today React gave me an "unknown prop" warning:

In this example, I gave my div element an abc attribute, which is obviously invalid HTML.

I was surprised that my linter didn't pick up on this. Looking at the documentation, the name and description of the no-unknown-property rule lead me to believe that this should be caught, but that doesn't appear to be the case.

So, I suppose this is a feature request: add a rule to catch invalid DOM properties.

[ljharb]

Were you using spread props, or was it an explicit prop directly on a DOM element?

[ryb73]

It was explicit.

[ljharb]

I definitely think no-unknown-property should be erroring out on all the same DOM element props that React 15.3 now does.

[mvirbicianskas]

was this fixed at some point? I can confirm it doesn't work as expected :/

[ljharb]

@mvirbicianskas no, but a PR would be welcome.

[sjarva]

Phew. This issue looked like "nice and small", but well, was more detective work than I expected 😅

If anyone has more use cases than <div abc="foo" />, feel free to read through and comment on the PR #3377

[ryb73]

That's awesome, thanks @sjarva!