ED/EDMarketConnector
1
0
Fork 0
mirror of https://github.com/EDCD/EDMarketConnector.git synced 2025-04-13 07:47:14 +03:00
Code Issues Projects Releases Wiki Activity

fixed some sentence construction

Browse Source
This commit is contained in:
A_D 2020-09-09 23:23:15 +02:00
parent 009ded50a1
commit ee12b2073c
No known key found for this signature in database
GPG Key ID: 4BE9EB7DF45076C4
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Contributing.md
View File

@ -194,9 +194,9 @@ and another for the Pull Request, merging or cherry-picking commits as needed.
Yes, this means using 'color' rather than 'colour', and in general will mean US, not British, spellings.
## **ALWAYS** place a single-statement control flow body
## Control flow
e.g." control statements such as `if`, `else`, `for`, `foreach`, on a separate line, with consistent indentation.
Never oneline any control flow (`if`, `else`, `for`), as it makes spotting what happens next difficult.
Yes:
@ -213,7 +213,9 @@ if something_true: one_thing_we_do()
Yes, some existing code still flouts this rule.
### **Always** use Line breaks after scope changes. It makes reading code far easier
### Scope changes
**Always** use Line breaks after scope changes. It makes seeing where scope has changed far easier on a quick skim
Yes: