aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJens Rantil2013-05-22 21:07:17 +0100
committerPete Bacon Darwin2013-05-22 21:09:20 +0100
commit9d19b512e0aefa15dc832f08512b6ed38d23750f (patch)
tree32d8ad6e5782e8a9ff69f4ec67d2c19d6328e8c6
parenteef8f3438dfa2c279e92f30d0cd70e73ee9b6742 (diff)
downloadangular.js-9d19b512e0aefa15dc832f08512b6ed38d23750f.tar.bz2
docs(guide/directive): clarify directive priority
Fixes #2644.
-rw-r--r--docs/content/guide/directive.ngdoc5
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/content/guide/directive.ngdoc b/docs/content/guide/directive.ngdoc
index e39cdbea..72146125 100644
--- a/docs/content/guide/directive.ngdoc
+++ b/docs/content/guide/directive.ngdoc
@@ -332,8 +332,9 @@ compiler}. The attributes are:
* `priority` - When there are multiple directives defined on a single DOM element, sometimes it
is necessary to specify the order in which the directives are applied. The `priority` is used
- to sort the directives before their `compile` functions get called. Higher `priority` goes
- first. The order of directives within the same priority is undefined.
+ to sort the directives before their `compile` functions get called. Priority is defined as a
+ number. Directives with greater numerical `priority` are compiled first. The order of directives with
+ the same priority is undefined. The default priority is `0`.
* `terminal` - If set to true then the current `priority` will be the last set of directives
which will execute (any directives at the current priority will still execute