You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the converted json and parsing into a java or javascript (or other) object model, characters like - (dash) and _ (underscore) cause the user to use the object['property-name'] type of syntax instead of object.propertyName
Please add an option to remove those characters and simply use camel case for json properties.
The text was updated successfully, but these errors were encountered:
While these key names aren't technically invalid JSON, I understand that the consensus seems to be in favor of camel case. The fact that it would improve compatibility with object models is big plus. In hindsight, it probably would have been better to have started that way a few years ago.
I think that adding an option so that both styles are available is a good idea. Thanks.
When using the converted json and parsing into a java or javascript (or other) object model, characters like - (dash) and _ (underscore) cause the user to use the
object['property-name']
type of syntax instead ofobject.propertyName
Please add an option to remove those characters and simply use camel case for json properties.
The text was updated successfully, but these errors were encountered: