Skip to content

Move from CamelCase to '_' casing #116

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.

Sign up for GitHub

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

Jump to bottom
Closed
kimchy opened this issue Apr 4, 2010 · 1 comment
Closed

Move from CamelCase to '_' casing #116

kimchy opened this issue Apr 4, 2010 · 1 comment
Labels
>enhancement v0.06.0

Comments

@kimchy
Copy link
Member

kimchy commented Apr 4, 2010

Seems like most nosql and json based rest interfaces use '_' instead of CamelCase. Changes include:

  1. All HTTP parameters move from CamelCase to '_' casing.
  2. All JSON requests and responses move from CamelCase to '_' casing.
  3. All settings now support both CamelCase as well as '_'.
@kimchy
Copy link
Member Author

kimchy commented Apr 4, 2010

Move from CamelCase to '_' casing, closed by 3b5b4b4.

@bluelu bluelu mentioned this issue Dec 11, 2014
Closed
@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
@felipe-fg felipe-fg mentioned this issue Dec 19, 2017
Closed
@david-sitsky david-sitsky mentioned this issue Mar 20, 2018
Closed
@fgdgtz183 fgdgtz183 mentioned this issue Jun 5, 2019
Closed
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@dliappis
Pin Vagrant box version
5f251e5 
The existing night-rally fixtures rely on a Ansible versions <2.8.
Pin box version to ensure it uses Vagrant images that come with
Ansible <2.8.

Relates elastic#116
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>enhancement v0.06.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy