"Why do we [scope], Master Wayne? So we can [stay modular and code like a rockstar]"
- Alfred (if he'd been an Angular developer)
As you've likely seen so far, the scope object within Angular serves as the primary intersection point between our data, our view, and the rest of our code. Any property or method that's available on our scope can be accessed and used within our HTML. Likewise, any changes that happen to the data will update the HTML and can trigger other updates within the rest of code, via the
$watch method that we've already used several times.
Those qualities of scope pervade nearly all of Angular development. Within a directive however, scoping takes on an even more powerful role, allowing us ...