Changing className -> class and onChange -> onInput is going to affect practical... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

svachalek on Sept 1, 2018 | parent | context | favorite | on: React Fire: Modernizing React DOM

Changing className -> class and onChange -> onInput is going to affect practically every React component ever written.

They seem to have opposite rationales (class is less pedantic and onInput is more pedantic) and I expect at least one of them will get dropped along the way but we'll see.

Klathmon on Sept 1, 2018 | [–]

They almost always provide codemods which can automatically convert a codebase for you, and they work pretty damn well.

And while I'm not sure if I'm on board with all of the changes, I'm in no way worried about having to do anything instantly.

madeofpalk on Sept 1, 2018 | [–]

The rationale seems to be "default to plain html/dom" where possible.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact