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

Guidelines.md - JSON properties names should be in lowerCamelCase. #415

Open

pantafive wants to merge 1 commit into microsoft:vNext from pantafive:patch-1

pantafive commented Nov 9, 2022 •

edited

Loading

Clarify that the JSON properties names should be in lowerCamelCase.

17.2. Casing

Acronyms SHOULD follow the casing conventions as though they were regular words (e.g. Url).
All identifiers including namespaces, entityTypes, entitySets, properties, actions, functions and enumeration values SHOULD use lowerCamelCase.
HTTP headers are the exception and SHOULD use standard HTTP convention of Capitalized-Hyphenated-Terms.

https://github.com/microsoft/api-guidelines/blob/vNext/Guidelines.md#172-casing


          Guidelines.md

073a220

Clarify that the JSON properties names should be in lowerCamelCase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet