SashLilac/cambridge
1
0
Fork 0
mirror of https://github.com/SashLilac/cambridge.git synced 2024-11-22 02:39:03 -06:00
Code Issues Projects Releases Wiki Activity

Removed a stupid exception to the mixing-tabs-and-spaces rule.

Browse Source 
I apologize that it took me 2 years to think of this workaround.
This commit is contained in:
Joe Zeng 2021-11-09 14:48:05 -05:00 committed by GitHub
parent 9381091110
commit 18e0e02c76
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
CONTRIBUTING.md
View File

@ -57,13 +57,13 @@ Coding conventions
Use tabs to indent, spaces to align. Use tabs to indent, spaces to align.
* Specifically, spaces should not appear at the beginning of a line, and tabs should not appear _except_ at the beginning of a line. * Specifically, spaces should not appear at the beginning of a line, and tabs should not appear _except_ at the beginning of a line.
* The sole exception is in a multiline `if` statement; the initial `if` should have four spaces before it to align it with an `elseif` on the next line. For example: * If you're aligning multiline if-statements, the initial "if", "elseif" or "else" should be flush left with the indentation level, with spaces padding the gap to the next word as necessary. For example:
```lua ```lua
---- 4 spaces if self.level < 900 then return 12
if self.level < 900 then return 12 elseif self.level < 1200 then return 8
elseif self.level < 1200 then return 8 else return 6
else return 6 end end
``` ```
Comments at the end of lines of code must be one line long. Multi-line comments must appear in their own block. Comments at the end of lines of code must be one line long. Multi-line comments must appear in their own block.