From 82d90a409692e97a79c3bf4708ee80796c7de2d6 Mon Sep 17 00:00:00 2001
From: Igor Minar
Date: Fri, 6 Apr 2012 16:35:17 -0700
Subject: fix(docs): change all directive references to use the normalized
names
---
src/ng/directive/a.js | 4 +-
src/ng/directive/booleanAttrs.js | 44 +++++++++---------
src/ng/directive/form.js | 21 +++++----
src/ng/directive/input.js | 96 +++++++++++++++++++--------------------
src/ng/directive/ngBind.js | 40 +++++++++-------
src/ng/directive/ngClass.js | 30 ++++++------
src/ng/directive/ngCloak.js | 12 ++---
src/ng/directive/ngController.js | 8 ++--
src/ng/directive/ngEventDirs.js | 56 +++++++++++------------
src/ng/directive/ngInclude.js | 17 +++----
src/ng/directive/ngInit.js | 6 +--
src/ng/directive/ngNonBindable.js | 6 +--
src/ng/directive/ngPluralize.js | 16 +++----
src/ng/directive/ngRepeat.js | 10 ++--
src/ng/directive/ngShowHide.js | 12 ++---
src/ng/directive/ngStyle.js | 6 +--
src/ng/directive/ngSwitch.js | 14 +++---
src/ng/directive/ngTransclude.js | 2 +-
src/ng/directive/ngView.js | 12 ++---
src/ng/directive/script.js | 2 +-
src/ng/directive/select.js | 26 +++++------
21 files changed, 224 insertions(+), 216 deletions(-)
(limited to 'src/ng/directive')
diff --git a/src/ng/directive/a.js b/src/ng/directive/a.js
index d96af784..04a77129 100644
--- a/src/ng/directive/a.js
+++ b/src/ng/directive/a.js
@@ -4,8 +4,8 @@
* Modifies the default behavior of html A tag, so that the default action is prevented when href
* attribute is empty.
*
- * The reasoning for this change is to allow easy creation of action links with ng-click without
- * changing the location or causing page reloads, e.g.:
+ * The reasoning for this change is to allow easy creation of action links with `ngClick` directive
+ * without changing the location or causing page reloads, e.g.:
* Save
*/
var htmlAnchorDirective = valueFn({
diff --git a/src/ng/directive/booleanAttrs.js b/src/ng/directive/booleanAttrs.js
index fee10ed8..c9f286fb 100644
--- a/src/ng/directive/booleanAttrs.js
+++ b/src/ng/directive/booleanAttrs.js
@@ -2,7 +2,7 @@
/**
* @ngdoc directive
- * @name angular.module.ng.$compileProvider.directive.ng-href
+ * @name angular.module.ng.$compileProvider.directive.ngHref
* @restrict A
*
* @description
@@ -10,8 +10,7 @@
* the page open to a wrong URL, if the user clicks that link before
* angular has a chance to replace the {{hash}} with actual URL, the
* link will be broken and will most likely return a 404 error.
- * The `ng-href` solves this problem by placing the `href` in the
- * `ng-` namespace.
+ * The `ngHref` directive solves this problem.
*
* The buggy way to write it:
*
@@ -24,7 +23,7 @@
*
*
* @element A
- * @param {template} ng-href any string which can contain `{{}}` markup.
+ * @param {template} ngHref any string which can contain `{{}}` markup.
*
* @example
* This example uses `link` variable inside `href` attribute:
@@ -83,15 +82,14 @@
/**
* @ngdoc directive
- * @name angular.module.ng.$compileProvider.directive.ng-src
+ * @name angular.module.ng.$compileProvider.directive.ngSrc
* @restrict A
*
* @description
- * Using markup like `{{hash}}` in a `src` attribute doesn't
+ * Using Angular markup like `{{hash}}` in a `src` attribute doesn't
* work right: The browser will fetch from the URL with the literal
- * text `{{hash}}` until replaces the expression inside
- * `{{hash}}`. The `ng-src` attribute solves this problem by placing
- * the `src` attribute in the `ng-` namespace.
+ * text `{{hash}}` until Angular replaces the expression inside
+ * `{{hash}}`. The `ngSrc` directive solves this problem.
*
* The buggy way to write it:
*
@@ -104,12 +102,12 @@
*
*
* @element IMG
- * @param {template} ng-src any string which can contain `{{}}` markup.
+ * @param {template} ngSrc any string which can contain `{{}}` markup.
*/
/**
* @ngdoc directive
- * @name angular.module.ng.$compileProvider.directive.ng-disabled
+ * @name angular.module.ng.$compileProvider.directive.ngDisabled
* @restrict A
*
* @description
@@ -124,7 +122,7 @@
* The HTML specs do not require browsers to preserve the special attributes such as disabled.
* (The presence of them means true and absence means false)
* This prevents the angular compiler from correctly retrieving the binding expression.
- * To solve this problem, we introduce ng-disabled.
+ * To solve this problem, we introduce the `ngDisabled` directive.
*
* @example
@@ -142,20 +140,20 @@
*
* @element INPUT
- * @param {string} expression Angular expression that will be evaluated.
+ * @param {expression} ngDisabled Angular expression that will be evaluated.
*/
/**
* @ngdoc directive
- * @name angular.module.ng.$compileProvider.directive.ng-checked
+ * @name angular.module.ng.$compileProvider.directive.ngChecked
* @restrict A
*
* @description
* The HTML specs do not require browsers to preserve the special attributes such as checked.
* (The presence of them means true and absence means false)
* This prevents the angular compiler from correctly retrieving the binding expression.
- * To solve this problem, we introduce ng-checked.
+ * To solve this problem, we introduce the `ngChecked` directive.
* @example
@@ -172,20 +170,20 @@
*
* @element INPUT
- * @param {string} expression Angular expression that will be evaluated.
+ * @param {expression} ngChecked Angular expression that will be evaluated.
*/
/**
* @ngdoc directive
- * @name angular.module.ng.$compileProvider.directive.ng-multiple
+ * @name angular.module.ng.$compileProvider.directive.ngMultiple
* @restrict A
*
* @description
* The HTML specs do not require browsers to preserve the special attributes such as multiple.
* (The presence of them means true and absence means false)
* This prevents the angular compiler from correctly retrieving the binding expression.
- * To solve this problem, we introduce ng-multiple.
+ * To solve this problem, we introduce the `ngMultiple` directive.
*
* @example
@@ -208,20 +206,20 @@
*
* @element SELECT
- * @param {string} expression Angular expression that will be evaluated.
+ * @param {expression} ngMultiple Angular expression that will be evaluated.
*/
/**
* @ngdoc directive
- * @name angular.module.ng.$compileProvider.directive.ng-readonly
+ * @name angular.module.ng.$compileProvider.directive.ngReadonly
* @restrict A
*
* @description
* The HTML specs do not require browsers to preserve the special attributes such as readonly.
* (The presence of them means true and absence means false)
* This prevents the angular compiler from correctly retrieving the binding expression.
- * To solve this problem, we introduce ng-readonly.
+ * To solve this problem, we introduce the `ngReadonly` directive.
* @example
@@ -244,14 +242,14 @@
/**
* @ngdoc directive
- * @name angular.module.ng.$compileProvider.directive.ng-selected
+ * @name angular.module.ng.$compileProvider.directive.ngSelected
* @restrict A
*
* @description
* The HTML specs do not require browsers to preserve the special attributes such as selected.
* (The presence of them means true and absence means false)
* This prevents the angular compiler from correctly retrieving the binding expression.
- * To solve this problem, we introduce ng-selected.
+ * To solve this problem, we introduced the `ngSelected` directive.
* @example
diff --git a/src/ng/directive/form.js b/src/ng/directive/form.js
index f688b542..ecb47ebe 100644
--- a/src/ng/directive/form.js
+++ b/src/ng/directive/form.js
@@ -124,7 +124,7 @@ function FormController(element, attrs) {
/**
* @ngdoc directive
- * @name angular.module.ng.$compileProvider.directive.ng-form
+ * @name angular.module.ng.$compileProvider.directive.ngForm
* @restrict EAC
*
* @description
@@ -132,7 +132,7 @@ function FormController(element, attrs) {
* does not allow nesting of form elements. It is useful to nest forms, for example if the validity of a
* sub-group of controls needs to be determined.
*
- * @param {string=} ng-form|name Name of the form. If specified, the form controller will be published into
+ * @param {string=} ngForm|name Name of the form. If specified, the form controller will be published into
* related scope, under this name.
*
*/
@@ -149,11 +149,11 @@ function FormController(element, attrs) {
* If `name` attribute is specified, the form controller is published onto the current scope under
* this name.
*
- * # Alias: {@link angular.module.ng.$compileProvider.directive.ng-form `ng-form`}
+ * # Alias: {@link angular.module.ng.$compileProvider.directive.ngForm `ngForm`}
*
* In angular forms can be nested. This means that the outer form is valid when all of the child
* forms are valid as well. However browsers do not allow nesting of `