Camelcase all keys

[lucaswoj]

From @lucaswoj on December 23, 2016 14:41

Working with Mapbox style spec objects in Javascript is less ergonomic because all the dashcase properties must be quoted when they are used as identifiers.

var layer = { 'line-color': 'blue' }
layer['line-color']

vs

var layer = { lineColor: 'blue' }
layer.lineColor

They look odd in conjunction with the camelcased source properties #175

Copied from original issue: mapbox/mapbox-gl-style-spec#638

[lucaswoj]

From @tmcw on December 23, 2016 14:58

Oof, that is one breaking change, but I support it 100%. We used dashes in CartoCSS too, from the CSS lineage, and in simplestyle-spec, and they're just inconvenient for no reason. This would also bring property names closer to what @1ec5 wants on the native side.

[lucaswoj]

From @1ec5 on December 23, 2016 18:5

I have no opinion either way. Camel case is always applied systematically, so it poses no barrier to people developing against our Android, iOS, or macOS SDKs, where we’ve exposed symbolic constants or method names instead of requiring strings to be hard-coded (as JavaScript does). Besides, the Android SDK uses SCREAMING_SNAKE_CASE too.

[jfirebaugh]

Closing here; see #6584.