-
Notifications
You must be signed in to change notification settings - Fork 14
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
Rules for JSON formatting #206
Comments
I would vote for the second option for formatting, if we were voting. |
No preference here... beyond a vote for consistency. |
Likewise no prefernce...second it is then. |
I have preference for the first form (which I why I used it)... so down to @rosy1280 to tie break |
:tumbleweed: @rosy1280 , @julianmorley please speak up. |
Oops, sorry @neilsjefferies |
i vote for option 1 |
option 1 |
Assigning to myself for PR |
ahankinson
added a commit
that referenced
this issue
Oct 17, 2018
Fixes #206 Also removed tabs from the Moab examples
Merged
zimeon
pushed a commit
that referenced
this issue
Oct 17, 2018
* Formatting JSON Fixes #206 Also removed tabs from the Moab examples * Fixed missing spaces
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I see one major inconsistency in our JSON formatting: are there spaces inside
[
and]
. ie.or
I note that the Moab examples have two spaces after the
:
in the state blocks, which should also be changed to one.The text was updated successfully, but these errors were encountered: