AngularJS : Differences among = & @ in directive scope?

Question

Creating an isolate scope inside a directive lets us map the outer scope to the inner scope. We have seen six different ways to map to attrbutes:

1. =attr
2. &attr
3. @attr
4. =
5. &
6. @

What do each of these scope mapping options do?

Answer 1

This can be confusing but hopefully a simple example will clarify it. First, let's separate model bindings from behaviors.

Here is a fiddle that should help tie things together: http://jsfiddle.net/jeremylikness/3pvte/

And explained ... if your directive looks like this:

<my-directive target="foo"/> 

Then you have these possibilities for scope:

{ target : '=' } 

This will bind scope.target (directive) to $scope.foo (outer scope). This is because = is for two-way binding and when you don't specify anything, it automatically matches the name on the inner scope to the name of the attribute on the directive. Changes to scope.target will update $scope.foo.

{ bar : '=target' } 

This will bind scope.bar to $scope.foo. This is because again we specify two-way binding, but tell the directive that what is in the attribute "target" should appear on the inner scope as "bar". Changes to scope.bar will update $scope.foo.

{ target : '@' } 

This will set scope.target to "foo" because @ means "take it literally." Changes to scope.target won't propagate outside of your directive.

{ bar : '@target' } 

This will set scope.bar to "foo" because @ takes it's value from the target attribute. Changes to scope.bar won't propagate outside of your directive.

Now let's talk behaviors. Let's assume your outer scope has this:

$scope.foo = function(parm1, parm2) { console.log(parm1 + ": " + parm2); } 

There are several ways you can access this. If your HTML is:

<my-directive target='foo'>

Then

{ target : '=' } 

Will allow you to call scope.target(1,2) from your directive.

Same thing,

{ bar : '=target' }

Allows you to call scope.bar(1,2) from your directive.

The more common way is to establish this as a behavior. Technically, ampersand evaluates an expression in the context of the parent. That's important. So I could have:

<my-directive target="a+b" />

And if the parent scope has $scope.a = 1 and $scope.b = 2, then on my directive:

{ target: '&' } 

I can call scope.target() and the result will be 3. This is important - the binding is exposed as a function to the inner scope but the directive can bind to an expression.

A more common way to do this is:

<my-directive target="foo(val1,val2)"> 

Then you can use:

{ target: '&' }

And call from the directive:

scope.target({val1: 1, val2: 2}); 

This takes the object you passed, maps the properties to parameters in the evaluated expression and then calls the behavior, this case calling $scope.foo(1,2);

You could also do this:

<my-directive target="foo(1, val)"/>

This locks in the first parameter to the literal 1, and from the directive:

{ bar: '&target' }

Then:

scope.bar(5) 

Which would call $scope.foo(1,5);