This is interesting
> Instead of ignoring unrecognized HTML and SVG attributes, React will now pass them through to the DOM.
Does that mean we can start using "class" instead of "className"?
> Instead of ignoring unrecognized HTML and SVG attributes, React will now pass them through to the DOM.
Does that mean we can start using "class" instead of "className"?
[1]: https://developer.mozilla.org/en-US/docs/Web/API/Element/cla...
[2]: https://developer.mozilla.org/en-US/docs/Web/API/HTMLLabelEl...
const { class } = props
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.)
> Note: always use the canonical React naming for all supported attributes.
Looking through the examples, it looks like non-string class values will be converted to strings, while non-string className values will be ignored (with a warning).
[0] https://facebook.github.io/react/blog/2017/09/08/dom-attribu...