docs: cleanup config formatting #7336
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aschmahmann
force-pushed
the
docs/config-formatting
branch
from
dbb1c8a
to
a0e0150
Compare
Stebalien
approved these changes
May 20, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GitHub shows big red highlighted text through the document when doing a diff (e.g. on future PRs) if the code fragments labeled JSON appear to be improperly formatted. I've just gone and added some curly braces.
If we think they're a pain/annoying we can just drop this PR. Additionally, if we'd like to remove the wrapping
{}that is around some, but not all of the json fragments to make them smaller I'm fine doing that as well.