Skip to content
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

camelCase or snake_case in client guidelines #124

Closed
christophfriedrich opened this issue Sep 27, 2018 · 1 comment
Closed

camelCase or snake_case in client guidelines #124

christophfriedrich opened this issue Sep 27, 2018 · 1 comment
Milestone

Comments

@christophfriedrich
Copy link
Contributor

I only just realised that the method names in the client guidelines are given in camelCase, but the parameters are given in snake_case. Is this on purpose?

The doc explicitly states that the "case to your liking" policy "applies for all names, including scopes, method names and parameters". It doesn't explicitly say "but please stick to ONE casing", but I'm pretty sure that this is implied and therefore suggest that the examples should stick to one casing, too.

christophfriedrich added a commit to christophfriedrich/openeo-api that referenced this issue Sep 27, 2018
m-mohr added a commit that referenced this issue Oct 5, 2018
@m-mohr m-mohr added this to the v0.4 milestone Oct 12, 2018
@m-mohr
Copy link
Member

m-mohr commented Oct 12, 2018

Should be fixed by the referenced commit.

@m-mohr m-mohr closed this as completed Oct 12, 2018
m-mohr added a commit that referenced this issue Oct 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants