format adjustment for style-guide.jade
This commit is contained in:
parent
67c9ef0c7a
commit
701af71eab
|
@ -210,11 +210,13 @@ a(href="#toc") 回到顶部
|
|||
.s-rule.do
|
||||
:marked
|
||||
**Do** define small functions
|
||||
|
||||
**坚持** 定义小的函数
|
||||
|
||||
.s-rule.consider
|
||||
:marked
|
||||
**Consider** limiting to no more than 75 lines.
|
||||
|
||||
**考虑** 限制在75行之内
|
||||
.s-why
|
||||
:marked
|
||||
|
@ -832,7 +834,7 @@ a(href="#toc") Back to top
|
|||
:marked
|
||||
**Why?** Provides a consistent way to quickly identify end-to-end tests.
|
||||
|
||||
*为什么?** 提供一致的方法快速识别端对端测试文件。
|
||||
**为什么?** 提供一致的方法快速识别端对端测试文件。
|
||||
|
||||
.s-why.s-why-last
|
||||
:marked
|
||||
|
@ -1007,6 +1009,7 @@ a(href="#toc") 回到顶部
|
|||
.s-why
|
||||
:marked
|
||||
**Why?** Follows conventional thinking for properties and methods.
|
||||
|
||||
**为何?** 遵循传统属性和方法的命名公约。
|
||||
|
||||
.s-why
|
||||
|
@ -1211,6 +1214,7 @@ a(href="#toc") 回到顶部
|
|||
.s-why.s-why-last
|
||||
:marked
|
||||
**Why?** We spend less time hunting and pecking for code, and become more efficient. If this means we want longer file names, then so be it.
|
||||
|
||||
**为何?** 我们花费更少的时间来查找和琢磨代码,工作更有效率。如果这意味着更长的文件名,那就让它去吧。
|
||||
|
||||
.l-sub-section
|
||||
|
@ -1362,7 +1366,7 @@ a(href="#toc") 回到顶部
|
|||
|
||||
.l-sub-section
|
||||
:marked
|
||||
While we prefer our Components to be in their own dedicated folder, another option for small apps is to keep Components flat (not in a dedicated folder). This adds up to four files to the existing folder, but also reduces the folder nesting. Be consistent.、
|
||||
While we prefer our Components to be in their own dedicated folder, another option for small apps is to keep Components flat (not in a dedicated folder). This adds up to four files to the existing folder, but also reduces the folder nesting. Be consistent.
|
||||
|
||||
虽然我们比较喜欢把组件放到它自己独立的目录里面,但是对于很小应用来说,另一个选项是保持结构平坦(不在自己独立的目录里)。这样我们添加最多四个文件到一个已有的目录,但是同时减少的目录的嵌套。保持前后一致就好。
|
||||
|
||||
|
@ -1709,8 +1713,7 @@ a(href="#toc") 回到顶部
|
|||
|
||||
.s-rule.do
|
||||
:marked
|
||||
**Do** put the contents of lazy loaded features in a *lazy loaded folder*.
|
||||
A typical *lazy loaded folder* contains a *routing component*, its child components, and their related assets and modules.
|
||||
**Do** put the contents of lazy loaded features in a *lazy loaded folder*. A typical *lazy loaded folder* contains a *routing component*, its child components, and their related assets and modules.
|
||||
|
||||
**坚持** 把懒惰加载特征的文件放到**懒惰加载目录**。典型的*懒惰加载目录*包含*路由组件*、子级组件和相关的东西和模块。
|
||||
|
||||
|
@ -1742,6 +1745,7 @@ a(href="#toc") 回到顶部
|
|||
.s-why
|
||||
:marked
|
||||
**Why?** Lazy loaded code paths are easily identifiable by their `+` prefix.
|
||||
|
||||
**为何?** 通过前缀`+`,懒惰加载源代码可以很容易被识别。
|
||||
|
||||
.s-why
|
||||
|
@ -1753,6 +1757,7 @@ a(href="#toc") 回到顶部
|
|||
.s-why.s-why-last
|
||||
:marked
|
||||
**Why?** If we see an `import` path that contains a `+`, we can quickly refactor to use lazy loading.
|
||||
|
||||
**为何?** 如果看到包含`+`的`导入`路径,我们能快速重构,使用懒惰加载。
|
||||
|
||||
.example-title Lazy Loaded Folders 懒惰加载目录
|
||||
|
|
Loading…
Reference in New Issue