From bf914e99759c9d354c6581744dea04c7f6a2cda4 Mon Sep 17 00:00:00 2001 From: Moonchild Date: Thu, 6 Feb 2020 14:47:30 +0100 Subject: Update UXP Coding Style.md Minor typo --- docs/UXP Coding Style.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/UXP Coding Style.md') diff --git a/docs/UXP Coding Style.md b/docs/UXP Coding Style.md index 83f59c8b1f..1a9568c542 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 +--> -- cgit v1.2.3