docs: update docs with all new 5.0 names (#866)

aboyton · mgechev · commit e2bce2473c61 · 2019-08-01T19:14:41.000-07:00
diff --git a/docs/rules/banana-in-box/index.html b/docs/rules/banana-in-box/index.html
@@ -1,5 +1,5 @@
 ---
-ruleName: banana-in-box
+ruleName: template-banana-in-box
 type: functionality
 description: Ensure that the two-way data binding syntax is correct.
 rationale: 'The parens "()" should have been inside the brackets "[]".'
@@ -8,6 +8,6 @@
 typescriptOnly: true
 hasFix: true
 layout: rule
-title: 'Rule: banana-in-box'
+title: 'Rule: template-banana-in-box'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/contextual-life-cycle/index.html b/docs/rules/contextual-life-cycle/index.html
@@ -5,10 +5,10 @@
 rationale: >-
   Some life cycle methods can only be used in certain class types.For example, ngOnInit() hook method should not be used in an @Injectable
   class.
-ruleName: contextual-life-cycle
+ruleName: contextual-lifecycle
 type: functionality
 typescriptOnly: true
 layout: rule
-title: 'Rule: contextual-life-cycle'
+title: 'Rule: contextual-lifecycle'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/decorator-not-allowed/index.html b/docs/rules/decorator-not-allowed/index.html
@@ -3,10 +3,10 @@
 options: null
 optionsDescription: Not configurable.
 rationale: 'Some decorators can only be used in certain class types. For example, an @Input should not be used in an @Injectable class.'
-ruleName: decorator-not-allowed
+ruleName: contextual-decorator
 type: functionality
 typescriptOnly: true
 layout: rule
-title: 'Rule: decorator-not-allowed'
+title: 'Rule: contextual-decorator'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/enforce-component-selector/index.html b/docs/rules/enforce-component-selector/index.html
@@ -1,12 +1,12 @@
 ---
-ruleName: enforce-component-selector
+ruleName: use-component-selector
 type: style
 description: Component selector must be declared.
 rationale: Omit the component selector makes debugging difficult.
 options: null
 optionsDescription: Not configurable.
 typescriptOnly: true
 layout: rule
-title: 'Rule: enforce-component-selector'
+title: 'Rule: use-component-selector'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/i18n/index.html b/docs/rules/i18n/index.html
@@ -18,13 +18,13 @@
   One (or both) of the following arguments must be provided:
   * `check-id` Makes sure i18n attributes have ID specified
   * `check-text` Makes sure there are no elements with text content but no i18n attribute
-      
+
 rationale: Makes the code more maintainable in i18n sense.
-ruleName: i18n
+ruleName: template-i18n
 type: maintainability
 typescriptOnly: true
 layout: rule
-title: 'Rule: i18n'
+title: 'Rule: template-i18n'
 optionsJSON: |-
   {
     "items": {
diff --git a/docs/rules/max-inline-declarations/index.html b/docs/rules/max-inline-declarations/index.html
@@ -23,13 +23,13 @@
   * `animations` - number > 0 defining the maximum allowed inline lines for animations. Defaults to 15.
   * `styles` - number > 0 defining the maximum allowed inline lines for styles. Defaults to 3.
   * `template` - number > 0 defining the maximum allowed inline lines for template. Defaults to 3.
-      
+
 rationale: 'Large, inline templates and styles obscure the component''s purpose and implementation, reducing readability and maintainability.'
-ruleName: max-inline-declarations
+ruleName: component-max-inline-declarations
 type: maintainability
 typescriptOnly: true
 layout: rule
-title: 'Rule: max-inline-declarations'
+title: 'Rule: component-max-inline-declarations'
 optionsJSON: |-
   {
     "items": {
diff --git a/docs/rules/no-attribute-parameter-decorator/index.html b/docs/rules/no-attribute-parameter-decorator/index.html
@@ -3,10 +3,10 @@
 options: null
 optionsDescription: Not configurable.
 rationale: '@Attribute is considered bad practice. Use @Input instead.'
-ruleName: no-attribute-parameter-decorator
+ruleName: no-attribute-decorator
 type: maintainability
 typescriptOnly: true
 layout: rule
-title: 'Rule: no-attribute-parameter-decorator'
+title: 'Rule: no-attribute-decorator'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/no-conflicting-life-cycle-hooks/index.html b/docs/rules/no-conflicting-life-cycle-hooks/index.html
@@ -8,11 +8,11 @@
   A directive typically should not use both DoCheck and OnChanges to respond
   to changes on the same input, as ngOnChanges will continue to be called when the
   default change detector detects changes.
-      
-ruleName: no-conflicting-life-cycle-hooks
+
+ruleName: no-conflicting-lifecycle
 type: maintainability
 typescriptOnly: true
 layout: rule
-title: 'Rule: no-conflicting-life-cycle-hooks'
+title: 'Rule: no-conflicting-lifecycle'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/no-life-cycle-call/index.html b/docs/rules/no-life-cycle-call/index.html
@@ -3,10 +3,10 @@
 options: null
 optionsDescription: Not configurable.
 rationale: Explicit calls to life cycle hooks could be confusing. Invoke life cycle hooks is the responsability of Angular.
-ruleName: no-life-cycle-call
+ruleName: no-lifecycle-call
 type: maintainability
 typescriptOnly: true
 layout: rule
-title: 'Rule: no-life-cycle-call'
+title: 'Rule: no-lifecycle-call'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/no-output-named-after-standard-event/index.html b/docs/rules/no-output-named-after-standard-event/index.html
@@ -3,10 +3,10 @@
 options: null
 optionsDescription: Not configurable.
 rationale: Listeners subscribed to an output with such a name will also be invoked when the native event is raised.
-ruleName: no-output-named-after-standard-event
+ruleName: no-output-native
 type: maintainability
 typescriptOnly: true
 layout: rule
-title: 'Rule: no-output-named-after-standard-event'
+title: 'Rule: no-output-native'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/no-queries-parameter/index.html b/docs/rules/no-queries-parameter/index.html
@@ -10,11 +10,11 @@
   can be modified only in a single place: in the directive's class. If you use the queries metadata
   property, you must modify both the property declaration inside the controller, and the metadata
   associated with the directive.
-      
-ruleName: no-queries-parameter
+
+ruleName: no-queries-metadata-property
 type: style
 typescriptOnly: true
 layout: rule
-title: 'Rule: no-queries-parameter'
+title: 'Rule: no-queries-metadata-property'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/no-template-call-expression/index.html b/docs/rules/no-template-call-expression/index.html
@@ -3,10 +3,10 @@
 options: null
 optionsDescription: Not configurable.
 rationale: The change detector will call functions used in templates very often. Use an observable instead.
-ruleName: no-template-call-expression
+ruleName: template-no-call-expression
 type: maintainability
 typescriptOnly: true
 layout: rule
-title: 'Rule: no-template-call-expression'
+title: 'Rule: template-no-call-expression'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/pipe-impure/index.html b/docs/rules/pipe-impure/index.html
@@ -1,12 +1,12 @@
 ---
-ruleName: pipe-impure
+ruleName: no-pipe-impure
 type: functionality
 description: Pipes cannot be declared as impure.
 rationale: Impure pipes do not perform well because they run on every change detection cycle.
 options: null
 optionsDescription: Not configurable.
 typescriptOnly: true
 layout: rule
-title: 'Rule: pipe-impure'
+title: 'Rule: no-pipe-impure'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/templates-no-negated-async/index.html b/docs/rules/templates-no-negated-async/index.html
@@ -5,14 +5,14 @@
 rationale: >
 
   Angular's async pipes emit null initially, prior to the observable emitting any values, or the promise resolving. This can cause
-  negations, like 
+  negations, like
 
   *ngIf="!(myConditional | async)" to thrash the layout and cause expensive side-effects like firing off XHR requests for a component which
   should not be shown.
-ruleName: templates-no-negated-async
+ruleName: template-no-negated-async
 type: functionality
 typescriptOnly: true
 layout: rule
-title: 'Rule: templates-no-negated-async'
+title: 'Rule: template-no-negated-async'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/trackBy-function/index.html b/docs/rules/trackBy-function/index.html
@@ -3,10 +3,10 @@
 options: null
 optionsDescription: Not configurable.
 rationale: The use of 'trackBy' is considered a good practice.
-ruleName: trackBy-function
+ruleName: template-use-track-by-function
 type: maintainability
 typescriptOnly: true
 layout: rule
-title: 'Rule: trackBy-function'
+title: 'Rule: template-use-track-by-function'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/use-host-property-decorator/index.html b/docs/rules/use-host-property-decorator/index.html
@@ -9,11 +9,11 @@
   can be modified only in a single place: in the directive's class. If you use the host metadata
   property, you must modify both the property declaration inside the controller, and the metadata
   associated with the directive.
-      
-ruleName: use-host-property-decorator
+
+ruleName: no-host-metadata-property
 type: style
 typescriptOnly: true
 layout: rule
-title: 'Rule: use-host-property-decorator'
+title: 'Rule: no-host-metadata-property'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/use-input-property-decorator/index.html b/docs/rules/use-input-property-decorator/index.html
@@ -9,11 +9,11 @@
   * If you ever need to rename the property name associated with @Input, you can modify it in a single place.
   * The metadata declaration attached to the directive is shorter and thus more readable.
   * Placing the decorator on the same line usually makes for shorter code and still easily identifies the property as an input.
-      
-ruleName: use-input-property-decorator
+
+ruleName: no-inputs-metadata-property
 type: style
 typescriptOnly: true
 layout: rule
-title: 'Rule: use-input-property-decorator'
+title: 'Rule: no-inputs-metadata-property'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/use-life-cycle-interface/index.html b/docs/rules/use-life-cycle-interface/index.html
@@ -4,10 +4,10 @@
 options: null
 optionsDescription: Not configurable.
 rationale: Interfaces prescribe typed method signatures. Use those signatures to flag spelling and syntax mistakes.
-ruleName: use-life-cycle-interface
+ruleName: use-lifecycle-interface
 type: maintainability
 typescriptOnly: true
 layout: rule
-title: 'Rule: use-life-cycle-interface'
+title: 'Rule: use-lifecycle-interface'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/use-output-property-decorator/index.html b/docs/rules/use-output-property-decorator/index.html
@@ -9,11 +9,11 @@
   * If you ever need to rename the event name associated with @Output, you can modify it in a single place.
   * The metadata declaration attached to the directive is shorter and thus more readable.
   * Placing the decorator on the same line usually makes for shorter code and still easily identifies the property as an output.
-      
-ruleName: use-output-property-decorator
+
+ruleName: no-outputs-metadata-property
 type: style
 typescriptOnly: true
 layout: rule
-title: 'Rule: use-output-property-decorator'
+title: 'Rule: no-outputs-metadata-property'
 optionsJSON: 'null'
 ---
diff --git a/docs/rules/use-view-encapsulation/index.html b/docs/rules/use-view-encapsulation/index.html
@@ -2,10 +2,10 @@
 description: Disallows using of ViewEncapsulation.None.
 options: null
 optionsDescription: Not configurable.
-ruleName: use-view-encapsulation
+ruleName: use-component-view-encapsulation
 type: maintainability
 typescriptOnly: true
 layout: rule
-title: 'Rule: use-view-encapsulation'
+title: 'Rule: use-component-view-encapsulation'
 optionsJSON: 'null'
 ---
diff --git a/docs/src/worker.ts b/docs/src/worker.ts
@@ -5,13 +5,13 @@ const rules = require('codelyzer');
 const rulesConfig = {
   'directive-selector': [true, 'attribute', 'sg', 'camelCase'],
   'component-selector': [true, 'element', 'sg', 'kebab-case'],
-  'use-input-property-decorator': true,
-  'use-output-property-decorator': true,
-  'use-host-property-decorator': true,
+  'no-inputs-metadata-property': true,
+  'no-outputs-metadata-property': true,
+  'no-host-metadata-property': true,
   'no-input-rename': true,
   'no-output-rename': true,
   'no-output-on-prefix': true,
-  'use-life-cycle-interface': true,
+  'use-lifecycle-interface': true,
   'use-pipe-transform-interface': true,
   'component-class-suffix': true,
   'directive-class-suffix': true,
