Skip to content

Conversation

@bajtos
Copy link
Member

@bajtos bajtos commented Apr 27, 2018

Our current convention is to treat abbreviations longer than 2
characters as regular words and capitalize only the first character.

We already use "Json" form across the codebase instead of "JSON".

This commit applies the same convention to the JSON Schema type
introduced by the recent commit e9e6b12 (see #1286).

Checklist

  • npm test passes on your machine
  • New tests added or existing tests modified to cover all changes
  • Code conforms with the style guide
  • API Documentation in code was updated
  • Documentation in /docs/site was updated
  • Affected artifact templates in packages/cli were updated
  • Affected example projects in examples/* were updated

Our current convention is to treat abbreviations longer than 2
characters as regular words and capitalize only the first character.

We already use "Json" form across the codebase instead of "JSON".

This commit applies the same convention to the JSON Schema type
introduced by the recent commit e9e6b12.
@bajtos bajtos self-assigned this Apr 27, 2018
@virkt25
Copy link
Contributor

virkt25 commented Apr 27, 2018

hmm ... I'm ok with the change but I personally prefer JSONSchema or jsonSchema

@raymondfeng raymondfeng merged commit 1323bfb into master Apr 27, 2018
@bajtos bajtos deleted the refactor/rename-JSON-to-Json branch April 30, 2018 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants