-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid JSON (sort-of) #8
Comments
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: