Add 'when not to use curly braces' entry to style README #13
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.
Added first entry to the style guide, explaining that devs
should not surround one line code blocks under if / else / while
statements with {curly braces}.
This patch was created in response to a comment in PR #3134
bisq-network/bisq#3134 (comment)
Since this is the first entry, and no protocol for asciidoc usage
has been defined, there will eventually need to be some discussion
about breaking up the readme into a table of contents linking to
sub-docs, and consistent usage of the asciidoc syntax.