diff options
| author | Jens Rantil | 2013-05-20 18:31:39 +0200 |
|---|---|---|
| committer | Pete Bacon Darwin | 2013-05-21 13:17:51 +0100 |
| commit | 7f597a75090167cd1fad9df9fe67165d0da9fa11 (patch) | |
| tree | 85c7816a6fe728534f86675503f6cb41ea06c8e9 | |
| parent | 907d2f521e859491180518620538122ed138dfbf (diff) | |
| download | angular.js-7f597a75090167cd1fad9df9fe67165d0da9fa11.tar.bz2 | |
doc($compile): clarify compile function return value
If a compile function (within a directive) returns a function, it is a
post-link function.
Closes: #2713
| -rw-r--r-- | docs/content/guide/directive.ngdoc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/content/guide/directive.ngdoc b/docs/content/guide/directive.ngdoc index 22dd639e..e39cdbea 100644 --- a/docs/content/guide/directive.ngdoc +++ b/docs/content/guide/directive.ngdoc @@ -480,8 +480,8 @@ done in a linking function rather than in a compile function. A compile function can have a return value which can be either a function or an object. -* returning a function - is equivalent to registering the linking function via the `link` property - of the config object when the compile function is empty. +* returning a (post-link) function - is equivalent to registering the linking function via the + `link` property of the config object when the compile function is empty. * returning an object with function(s) registered via `pre` and `post` properties - allows you to control when a linking function should be called during the linking phase. See info about |