React: Reword "unknown property" warning to be less obnoxious

[gaearon]

I thought before it might cause knee jerk reactions, and it does in practice: https://twitter.com/freeformflo/status/928454078903894016

I think we should change the phrasing to a more neutral one. Potentially explaining why we prefer camel case.

[25564]

What about something simple along the lines of "Warning: Please use camel case property names. Did you mean tabIndex".

[skiritsis]

I could take this.

[cyan33]

If nobody is working on that, I could take this.

And IMHO, "Warning: Please use camelCase property names, rather than the html standardized ones, because it's more natural to work around with js" would be more straight-forward.

[skiritsis]

@thomasyimgit Working on it at the moment.

[bsutt123]

Is this issue resolved/taken? Facebook told me to wait for 2 weeks of inactivity before asking, but if I'm being honest it seems like the rewording is good.

If the rewording isn't sufficient, can you elaborate a bit on why so I can further refine it?

[nazihahmed]

another 2 weeks and the issue is still going, can anyone review the proposed solution?
if not I can fix it if there's anything wrong with his.

[renatoalencar]

HTML is not case sensitive so tabindex and tabIndex, right? The point is that it is JSX not HTML. I think the message could include something like "The JSX standard (different from the HTML standard) is case sensitive".

[photonite]

I would like to work on it.

[dnl228]

I am trying to get into the open source community and would like to find a simple issue to fix to get me started. Is anyone still working on this issue? If not I would like to work on it.

[mueedc]

If this issue is still available I'd love to tackle it and contribute to an open source project I use every day

"Adding Props are often declared as objects, later read or transformed, before passing down to DOM would provide a little more clarity as to why camelCase is preferred, rather than just ensuring JS reserved words are not being used."

[gaearon]

another 2 weeks and the issue is still going, can anyone review the proposed solution?

Sorry, it was the end of the year and we were scrambling to finish the current projects and then went on holidays. That's why the issue got no attention.

I filed https://github.com/reactjs/reactjs.org/issues/484 which I think is a pre-requisite to really fixing this. If you want to help, please chime in there (but it's not a very easy task).