From 51a7f9dc4ae4cb52be3599a172d0c1d9c44bfc8e Mon Sep 17 00:00:00 2001 From: Roy Ling Date: Tue, 14 Jan 2014 15:44:31 +0800 Subject: docs(guide/directive): rephrase for consistency - referring to `=attr` rather than `=prop` is consistent with note under example with =customerInfo - change `prop` to `attr` (basically `prop` refers to property in JS object, `attr` is for HTML tag) - change the function name in description to match the name in code example Closes #5786 --- docs/content/guide/directive.ngdoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/content/guide/directive.ngdoc') diff --git a/docs/content/guide/directive.ngdoc b/docs/content/guide/directive.ngdoc index 32877dd0..dd883cf3 100644 --- a/docs/content/guide/directive.ngdoc +++ b/docs/content/guide/directive.ngdoc @@ -734,13 +734,13 @@ own behavior to it. We want to run the function we pass by invoking it from the directive's scope, but have it run in the context of the scope where its registered. -We saw earlier how to use `=prop` in the `scope` option, but in the above example, we're using -`&prop` instead. `&` bindings expose a function to an isolated scope allowing the isolated scope +We saw earlier how to use `=attr` in the `scope` option, but in the above example, we're using +`&attr` instead. `&` bindings expose a function to an isolated scope allowing the isolated scope to invoke it, but maintaining the original scope of the function. So when a user clicks the -`x` in the dialog, it runs `Ctrl`'s `close` function. +`x` in the dialog, it runs `Ctrl`'s `hideDialog` function.
-**Best Practice:** use `&prop` in the `scope` option when you want your directive +**Best Practice:** use `&attr` in the `scope` option when you want your directive to expose an API for binding to behaviors.
-- cgit v1.2.3