Skip to content

Proposal to follow Google and Schema.org's JSON Style Guide: Use "camelCase" Naming Convention #1247

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

Closed
wants to merge 2 commits into from
Closed

Proposal to follow Google and Schema.org's JSON Style Guide: Use "camelCase" Naming Convention #1247

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
096362f
Updating Naming Convention to follow Google JSON Style Guide
garrettmac Dec 25, 2017
de55186
Updated JSON recommendation
garrettmac Feb 10, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Updated JSON recommendation 
removed Google Style Guide from spec
  • Loading branch information
@garrettmac
garrettmac authored Feb 10, 2018
commit de551866fa15f8fa40d7b8859a239c21c34913d3
14 changes: 6 additions & 8 deletions recommendations/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,16 +20,14 @@ The allowed and recommended characters for an URL safe naming of members are def

### JSON

Naming format should follows the [Google JSON Style Guide](https://google.github.io/styleguide/jsoncstyleguide.xml?showone=Property_Name_Format#Property_Name_Format), where:
It is important to adhere to a defined convention. Recommended property names **SHOULD** conform to the following guidelines:

> Property names must conform to the following guidelines:
- Property names **SHOULD** be camel-cased, ascii strings.
- First characters **SHOULD** be "a-z" (U+0061 to U+007A).
- Property names **SHOULD** be meaningful names with defined semantics.

> * Property names should be meaningful names with defined semantics.
> * Property names must be camel-cased, ascii strings.
> * The first character must be a letter, an underscore (_) or a dollar sign ($).
> * Subsequent characters can be a letter, a digit, an underscore, or a dollar sign.
> * Reserved JavaScript keywords should be avoided (A list of reserved JavaScript keywords can be found below).
> * These guidelines mirror the guidelines for naming JavaScript identifiers. This allows JavaScript clients to access properties using dot notation. (for example, result.thisIsAnInstanceVariable).

These guidelines mirror the guidelines for naming JavaScript identifiers. This allows JavaScript clients to access properties using dot notation.

> Here's an example of an object with one property:

Expand Down
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy