File tree 1 file changed +8
-2
lines changed 1 file changed +8
-2
lines changed Original file line number Diff line number Diff line change 9
9
6 . [ 测试] ( #测试 )
10
10
7 . [ 并发] ( #并发 )
11
11
8 . [ 错误处理] ( #错误处理 )
12
- 9 . [ 格式化] ( #formatting )
12
+ 9 . [ 格式化] ( #格式化 )
13
13
10 . [ 评论] ( #comments )
14
14
15
15
## 简介
@@ -2063,16 +2063,22 @@ getdata()
2063
2063
** [ ⬆ 返回顶部] ( #代码整洁的-javascript ) **
2064
2064
2065
2065
2066
- ## ** Formatting **
2066
+ ## ** 格式化 **
2067
2067
Formatting is subjective. Like many rules herein, there is no hard and fast
2068
2068
rule that you must follow. The main point is DO NOT ARGUE over formatting.
2069
2069
There are [ tons of tools] ( http://standardjs.com/rules.html ) to automate this.
2070
2070
Use one! It's a waste of time and money for engineers to argue over formatting.
2071
2071
2072
+ 格式化是主观的。 就像其它规则一样, 没有必须让你遵守的硬性规则。 重点是不要因为格式去争论, 这
2073
+ 里有[ 大量的工具] ( http://standardjs.com/rules.html ) 来自动格式化, 使用其中的一个即可! 因
2074
+ 为做为工程师去争论格式化就是在浪费时间和金钱。
2075
+
2072
2076
For things that don't fall under the purview of automatic formatting
2073
2077
(indentation, tabs vs. spaces, double vs. single quotes, etc.) look here
2074
2078
for some guidance.
2075
2079
2080
+ 针对自动格式化工具不能涵盖的问题(缩进、 制表符还是空格、 双引号还是单引号等), 这里有一些指南。
2081
+
2076
2082
### Use consistent capitalization
2077
2083
JavaScript is untyped, so capitalization tells you a lot about your variables,
2078
2084
functions, etc. These rules are subjective, so your team can choose whatever
You can’t perform that action at this time.
0 commit comments