Hacker News new | ask | show | jobs
by syntor 3185 days ago
I always assumed `class` was a keyword, which is why then went with `className` instead.
2 comments
sorahn 3185 days ago
both `className` and `htmlFor` are what the actual DOM uses. [1][2]

[1]: https://developer.mozilla.org/en-US/docs/Web/API/Element/cla...

[2]: https://developer.mozilla.org/en-US/docs/Web/API/HTMLLabelEl...

link
danabramov 3185 days ago
Yes, the reason is that you can't write something like

    const { class } = props
Which is very common and deeply confusing.

So even though "class" will technically work now, it will still warn, and ask that you use "className".

(And officially supporting both would make it confusing for third party components since each would have to also support both.)

link