more names

Author: johnpapa

public/docs/ts/latest/guide/style-guide.jade

@@ -75,11 +75,7 @@ a(id='toc')
 
 <a href="#toc">Back to top</a>
 :marked
-  ## File Naming
-
-  ### File Naming Guidelines
-  <a id="02-01"></a>
-  #### Style 02-01
+  ## Naming
 
     - Use consistent names for all components following a pattern that describes the component's feature then (optionally) its type. My recommended pattern is `feature.type.js`. There are 2 names for most assets:
       * the file name (`avengers.component.ts`)
@@ -93,7 +89,7 @@ a(id='toc')
 
 <a href="#toc">Back to top</a>
 :marked
-  ### Separate with Dots and Dashes
+  ### Separate File Names with Dots and Dashes
   <a id="02-01"></a>
   #### Style 02-01
 
@@ -111,58 +107,80 @@ a(id='toc')
 
 <a href="#toc">Back to top</a>
 :marked
-  ### Component Names
-  <a id="02-03"></a>
-  #### Style 02-03
+  ### Names
+  <a id="02-02"></a>
+  #### Style 02-02
 
-    - Use consistent names for all components named after their feature. Use UpperCamelCase for components' symbols. Match the name of the component to the naming of the file
+    - Use consistent names for all assets named after what they represent. 
+    
+    - Use UpperCamelCase for symbols. Match the name of the symbol to the naming of the file.
 
-      **Why?** Provides a consistent way to quickly identify and reference components.
+    - Append the symbol name with a suffix that it represents.
+
+      **Why?** Provides a consistent way to quickly identify and reference assets.
 
       **Why?** UpperCamelCase is conventional for identifying object that can be instantiated using a constructor.
 
+      **Why?** The `Component` suffix is more commonly used and is more explicitly descriptive.
+
     ```typescript
-    AppComponent            //app.component.ts
-    HeroesComponent       //heroes.component.ts
-    HeroListComponent    //hero-list.component.ts
-    HeroDetailComponent  //hero-detail.component.ts
+    /* recommended */
+    AppComponent         // app.component.ts
+    HeroesComponent      // heroes.component.ts
+    HeroListComponent    // hero-list.component.ts
+    HeroDetailComponent  // hero-detail.component.ts
+
+    /* recommended */
+    ValidationDirective  // validation.directive.ts
     ```
 
 <a href="#toc">Back to top</a>
 :marked
-  ### Suffixes
-  <a id="02-04"></a>
-  #### Style 02-04
+  ### Service Names
+  <a id="02-03"></a>
+  #### Style 02-03
 
-    - Append the component name with the suffix `Component`.
+    - Use consistent names for all services named after their feature. Use UpperCamelCase for services. Suffix services with `Service` when it is not clear what they are (e.g. when they are nouns).
 
-      **Why?** The `Component` suffix is more commonly used and is more explicitly descriptive.
+      **Why?** Provides a consistent way to quickly identify and reference services.
 
-      ```typescript
-      // recommended
+      **Why?** Clear service names such as `logger` do not require a suffix.
+
+      **Why?** Service names such as `Credit` are nouns and require a suffix and should be named with a suffix when it is not obvious if it is a service or something else. 
 
-      // hero-list.component.ts
-      export class HeroListComponent { }
+      ```typescript
+      HeroDataService    // hero-data.service.ts
+      CreditService      // credit.service.ts
+      LoggerService      // logger.service.ts
       ```
 
 <a href="#toc">Back to top</a>
 :marked
-  ### Service Names
-  <a id="02-10"></a>
-  #### Style 02-10
+  ### Bootstrapping
+  <a id="02-04"></a>
+  #### Style 02-04
 
-    - Use consistent names for all services named after their feature. Use UpperCamelCase for services. Suffix services with `Service` when it is not clear what they are (e.g. when they are nouns).
+    - Place bootstrapping and platform logic for the app in a file named `main.ts`.
+    
+    - Do not put app logic in the `main.ts`. Instead consider placing it in a Component or Service.
+    
+      **Why?** Follows a consistent convention for the startup logic of an app.
 
-      **Why?** Provides a consistent way to quickly identify and reference services.
+      **Why?** Follows a familar convention from other technology platforms.
 
-      **Why?** Clear service names such as `logger` do not require a suffix.
+<a href="#toc">Back to top</a>
+:marked
+  ### Pipe Names
+  <a id="02-10"></a>
+  #### Style 02-10
 
-      **Why?** Service names such as `Credit` are nouns and require a suffix and should be named with a suffix when it is not obvious if it is a service or something else. 
+    - Use consistent names for all pipes named after their feature. 
+
+      **Why?** Provides a consistent way to quickly identify and reference pipes.
 
       ```typescript
-      HeroService // hero.service.ts
-      CreditService  // credit.service.ts
-      Logger         // logger.service.ts
+      EllipsisPipe    // ellipsis.pipe.ts
+      InitCapsPipe    // init-caps.pipe.ts
       ```
 
 <a href="#toc">Back to top</a>
@@ -171,7 +189,7 @@ a(id='toc')
   <a id="02-12"></a>
   #### Style 02-12
 
-    - Name test specifications similar to the component they test with a suffix of `spec`.
+    - Name test specifications similar to the component they test with a suffix of `.spec`.
 
       **Why?** Provides a consistent way to quickly identify components.