anchor.diff:    ### 小函数
     <a id="01-02"></a>
     #### Style 01-02
  -  ### 风格01-02
  +  #### 风格01-02
   .s-rule.do
     :marked
       **Do** define small functions
       
  -    **坚持** 定义小的函数
  +    **坚持**定义小函数
   
   .s-rule.consider
     :marked
       **Consider** limiting to no more than 75 lines.
       
  -    **考虑** 限制在75行之内
  +    **考虑**限制在75行之内
   .s-why
     :marked
       **Why?** Small functions are easier to test, especially when they do one thing and serve one purpose.
       
  -    **为何？** 小函数更加易于测试，特别是当它们只做一件事，只为一个目的服务的时候。
  +    **为何？**小函数更易于测试，特别是当它们只做一件事，只为一个目的服务的时候。
   
   .s-why
     :marked
       **Why?** Small functions promote reuse.
       
  -    **为何？** 小函数促进了代码的重用。
  +    **为何？**小函数促进了代码的重用。
   
   .s-why
     :marked
       **Why?** Small functions are easier to read.
       
  -    **为何？** 小函数更加易于阅读。
  +    **为何？**小函数更加易于阅读。
   
   .s-why
     :marked
       **Why?** Small functions are easier to maintain.
       
  -    **为何？** 小函数更加易于维护。
  +    **为何？**小函数更加易于维护。
   
   .s-why.s-why-last
     :marked
       **Why?** Small functions help avoid hidden bugs that come with large functions that share variables with external scope, create unwanted closures, or unwanted coupling with dependencies.
       
  -    **为何？** 小函数帮助避免一些大函数与外界互相共享变量时，容易造成的令人讨厌的闭包和依赖联结等隐蔽错误。
  +    **为何？**小函数帮助避免一些大函数容易产生的那些与外界共享变量、创建意外的闭包或与依赖之间产生意外耦合等隐蔽的错误。
   
   a(href="#toc") Back to top
   
  
positive.code: 
  a(href="#toc") Back to top
  
  .l-main-section
  :marked
    ### End to End Test File Names
    ### 端对端测试文件命名
    <a id="02-11"></a>
    #### Style 02-11
    #### 风格02-11
  
negative.code:   :marked
      **Do** define one thing (e.g. service or component) per file.
      
      **坚持**每个文件只定义一样东西（比如服务或者组件）。
  
  .s-rule.consider
    :marked
      **Consider** limiting files to 400 lines of code.
      
      **考虑**把文件大小限制在400行代码以内。
  
  .s-why
    :marked
      **Why?** One component per file makes it far easier to read, maintain, and avoid collisions with teams in source control.
      
      **为何？**单组件文件非常容易阅读、维护，并能防止在版本控制系统里与团队冲突。
  
  .s-why
    :marked
      **Why?** One component per file avoids hidden bugs that often arise when combining components in a file where they may share variables, create unwanted closures, or unwanted coupling with dependencies.
      
      **为何？**单组件文件可以防止一些隐蔽的程序缺陷，当把多个组件合写在同一个文件中时，可能造成共享变量、创建意外的闭包，或者与依赖之间产生意外耦合等情况。
  
  .s-why.s-why-last
    :marked
      **Why?** A single component can be the default export for its file which facilitates lazy loading with the Component Router.
      
      **为何？**单独的组件通常是该文件默认的输出，这样就可以利用组件路由器实现按需加载。
      
  :marked
    The key is to make the code more reusable, easier to read, and less mistake prone.
  