@@ -119,7 +119,6 @@ Unless otherwise specified, the following applies to all code:
119
119
2. " Conflicted" typically refers to a getter which wants the same name as the underlying variable .
120
120
20. Prefer readonly members over getters backed by a variable , unless an internal setter is required .
121
121
21. Prefer Interfaces for object definitions , and types for parameter - value - only declarations .
122
-
123
122
1. Note that an explicit type is optional if not expected to be used outside of the function call,
124
123
unlike in this example:
125
124
@@ -153,7 +152,6 @@ Unless otherwise specified, the following applies to all code:
153
152
28. Export only what can be reused.
154
153
29. Prefer a type like `Optional<X >` (`type Optional<T > = T | null | undefined ` ) instead
155
154
of truly optional parameters.
156
-
157
155
1. A notable exception is when the likelihood of a bug is minimal, such as when a function
158
156
takes an argument that is more often not required than required. An example where the
159
157
` ? ` operator is inappropriate is when taking a room ID: typically the caller should
@@ -272,7 +270,6 @@ Unless otherwise specified, the following applies to all code:
272
270
interfaces have a habit of becoming more complex over time .
273
271
274
272
3. Inside a function , there is no need to comment every line , but consider :
275
-
276
273
- before a particular multiline section of code within the function , give an overview of what it does ,
277
274
to make it easier for a reader to follow the flow through the function as a whole .
278
275
- if it is anything less than obvious , explain _why_ we are doing a particular operation , with particular emphasis
0 commit comments