summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMoonchild <moonchild@palemoon.org>2020-02-06 14:47:30 +0100
committerwolfbeast <mcwerewolf@wolfbeast.com>2020-04-14 12:30:03 +0200
commit84d99e299629410008d28129a44739aac1a296dc (patch)
treebb62b9c9b5860f43e93856092e9ca2500252dcb8
parente29301f5d0fa6b8d5892169fa1d6b50798cbe94d (diff)
downloadUXP-84d99e299629410008d28129a44739aac1a296dc.tar
UXP-84d99e299629410008d28129a44739aac1a296dc.tar.gz
UXP-84d99e299629410008d28129a44739aac1a296dc.tar.lz
UXP-84d99e299629410008d28129a44739aac1a296dc.tar.xz
UXP-84d99e299629410008d28129a44739aac1a296dc.zip
Update UXP Coding Style.md
Minor typo
-rw-r--r--docs/UXP Coding Style.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/UXP Coding Style.md b/docs/UXP Coding Style.md
index 83f59c8b1..1a9568c54 100644
--- a/docs/UXP Coding Style.md
+++ b/docs/UXP Coding Style.md
@@ -13,7 +13,7 @@ The following formatting rules apply to all code:
- Always use spaces for indentation, never use tabs!
- Put a space between a keyword and parenthesis, e.g. `if (`.
- Put a space between variables and operators, e.g. `a == b`.
-- Put a space after a comma or semicolon in variable lists, e.g. `function (a, b, c)` or `for (i = 1; i < 10; i++)`.
+- Put a space after a comma or semicolon in variable lists, e.g. `function(a, b, c)` or `for (i = 1; i < 10; i++)`.
- Indentation of scopes is 2 spaces.
- Indentation of long lines is variable-aligned or expression-aligned (see "long line wrapping")
- Conditional defines are always placed on column 1. This is also true for nested defines.
@@ -236,4 +236,4 @@ ExMSw4MzQ2MjYwNDksLTE5MDMyNzE5OTYsLTEwMTIwMjc3ODMs
LTE4MzgzODM5MDIsODA5MjEzNTEyLC01Mzg0MjM4MDAsMzgyNj
I3NDYzLDIwODYwMjIwODUsLTE1MjU5MjE2MjIsLTY1OTMzMTA0
MCwtNzQwOTE5MDQ1LDE4Njc1NTQxNDJdfQ==
---> \ No newline at end of file
+-->