Add missing single-word attributes to property warning list

[nhunzaker]

I never added the all-lowercase words to the list of attribute casings to warn about. @flarnie caught this when you pass something like SiZe. This is a known HTML attribute. We need to warn users that they should specify this property as size.

Basically I just ran this over the 15.6.1 whitelist:

Object.keys(Properties)
      .filter(key => key === key.toLowerCase())
      .map(key => `${key}: '${key}',`).join('\n')

And pasted it over to the list.

[gaearon]

Why do we start from A three times? Are these generated from different whitelists? In this case should there be a comment explaining grouping
Or we could sort them all.

[nhunzaker]

Yes. It's a combination of the HTML Property Config and SVG Property Config, which where ultimately just blended into the same list inside of DOMProperty.properties

Wrestled with some editor-fu, but I've alphabetized these while still clumping together aliases.

[gaearon]

Accepted with nit (unclear sort order). Let's leave to @flarnie for second review.

[sophiebits]

Mind adding a test? A simple one is fine.

[nhunzaker]

@spicyj added a very basic test in de06c4a

[sophiebits]

loveit

[gaearon]

If we later add an attribute to whitelist should we also add it to this DEV whitelist?

[nhunzaker]

Yes. We could seed the list with existing property names from the whitelist, but i thought this was much simpler, even if duplicative

[gaearon]

Worth adding a comment to both maybe to make this clearer.

[nhunzaker]

Sure. Done!

…

On Fri, Aug 18, 2017, 6:48 PM Dan Abramov ***@***.***> wrote: Worth adding a comment to both maybe to make this clearer. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10495 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAkEOFQZe-7cTrJa_RM9XvXAVQIjPQYpks5sZhS_gaJpZM4O8DTR> .

[flarnie]

Thanks for doing this! I liked the helpful comments - I think this makes sense.

I'm going to do my testing work on top of this branch, assuming you will merge whenever you get a chance.