News for hackers. Stuff that matters.

A comment on React 16. Parent comment

Re:React 16 by syntor on Tuesday September 26, 2017 @03:55PM (#15342001)
I always assumed `class` was a keyword, which is why then went with `className` instead.
[ Parent | on HN ]
Re:React 16 by sorahn on Tuesday September 26, 2017 @04:59PM (#15342460)
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...

[ Parent | on HN ]
Re:React 16 by danabramov on Tuesday September 26, 2017 @06:15PM (#15343031)
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.)

[ Parent | on HN ]