Skip to content

Commit 0d4a323

Browse files
committed
formating
1 parent 881061c commit 0d4a323

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

README-zh-CN.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99
6. [测试](#测试)
1010
7. [并发](#并发)
1111
8. [错误处理](#错误处理)
12-
9. [格式化](#formatting)
12+
9. [格式化](#格式化)
1313
10. [评论](#comments)
1414

1515
## 简介
@@ -2063,16 +2063,22 @@ getdata()
20632063
**[⬆ 返回顶部](#代码整洁的-javascript)**
20642064

20652065

2066-
## **Formatting**
2066+
## **格式化**
20672067
Formatting is subjective. Like many rules herein, there is no hard and fast
20682068
rule that you must follow. The main point is DO NOT ARGUE over formatting.
20692069
There are [tons of tools](http://standardjs.com/rules.html) to automate this.
20702070
Use one! It's a waste of time and money for engineers to argue over formatting.
20712071

2072+
格式化是主观的。 就像其它规则一样, 没有必须让你遵守的硬性规则。 重点是不要因为格式去争论, 这
2073+
里有[大量的工具](http://standardjs.com/rules.html)来自动格式化, 使用其中的一个即可! 因
2074+
为做为工程师去争论格式化就是在浪费时间和金钱。
2075+
20722076
For things that don't fall under the purview of automatic formatting
20732077
(indentation, tabs vs. spaces, double vs. single quotes, etc.) look here
20742078
for some guidance.
20752079

2080+
针对自动格式化工具不能涵盖的问题(缩进、 制表符还是空格、 双引号还是单引号等), 这里有一些指南。
2081+
20762082
### Use consistent capitalization
20772083
JavaScript is untyped, so capitalization tells you a lot about your variables,
20782084
functions, etc. These rules are subjective, so your team can choose whatever

0 commit comments

Comments
 (0)