Skip to content
This repository has been archived by the owner on Jul 14, 2020. It is now read-only.

Should we use camelCase for all keys in JSON documents? #59

Closed
thomaseizinger opened this issue Apr 9, 2019 · 1 comment
Closed

Should we use camelCase for all keys in JSON documents? #59

thomaseizinger opened this issue Apr 9, 2019 · 1 comment

Comments

@thomaseizinger
Copy link
Contributor

There is this idea to make the JSON encoding the default and thereby postpone all decisions about other encodings to a later point: #57

If JSON is the default, we might consider using a more JSON-idiomatic naming convention for all fields: camelCase.
@thomaseizinger thomaseizinger changed the title Should we use camelCase for all field names in all messages Should we use camelCase for all keys in JSON documents? Apr 9, 2019
@D4nte D4nte added the icebox label Apr 10, 2019
@D4nte D4nte removed the icebox label May 8, 2019
@bonomat
Copy link
Member

bonomat commented Nov 3, 2019

Closing as this optimization does not seems to be important enough. (:

@bonomat bonomat closed this as completed Nov 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bonomat @D4nte @thomaseizinger