Skip to content

Commit 9d19b51

Browse files
Jens Rantilpetebacondarwin
Jens Rantil
authored andcommitted
docs(guide/directive): clarify directive priority
Fixes angular#2644.
1 parent eef8f34 commit 9d19b51

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/content/guide/directive.ngdoc

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -332,8 +332,9 @@ compiler}. The attributes are:
332332

333333
* `priority` - When there are multiple directives defined on a single DOM element, sometimes it
334334
is necessary to specify the order in which the directives are applied. The `priority` is used
335-
to sort the directives before their `compile` functions get called. Higher `priority` goes
336-
first. The order of directives within the same priority is undefined.
335+
to sort the directives before their `compile` functions get called. Priority is defined as a
336+
number. Directives with greater numerical `priority` are compiled first. The order of directives with
337+
the same priority is undefined. The default priority is `0`.
337338

338339
* `terminal` - If set to true then the current `priority` will be the last set of directives
339340
which will execute (any directives at the current priority will still execute

0 commit comments

Comments
 (0)