You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: GUIDELINES.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ function foo(bar = 'baz') {}
86
86
87
87
## Code blocks
88
88
89
-
Whenever writing an `if`/`else` statement, the `else` keyword should directly follow the closing curly brace from the `if` statement. No line break between the closing brace and the keyword should exist.
89
+
Whenever writing an `if`/`else` statement, the `else` keyword should directly follow the closing curly brace from the `if` statement. No line break between the closing brace and the keyword should exist.
90
90
91
91
Also, there should always be a single space between the `if` keyword and the condition.
92
92
@@ -104,7 +104,7 @@ Same goes with do/while and try/catch.
104
104
105
105
## Inline documentation
106
106
107
-
Every function should be documented using [JSDoc](). Annotations should not be aligned in order not to have to update alignment whever a longer line is added.
107
+
Every function should be documented using [JSDoc](http://usejsdoc.org/). Annotations should not be aligned in order not to have to update alignment whever a longer line is added.
108
108
109
109
```js
110
110
/**
@@ -125,7 +125,7 @@ cfg.post(config);
125
125
config.view= config; // Backward compatibility.
126
126
127
127
/**
128
-
* This is an extra long comment that does not fit on a single line because it
128
+
* This is an extra long comment that does not fit on a single line because it
129
129
* is longer than 80 characters. Because of this, it it splitted across several
0 commit comments