From 4804c83b7db5770d5d02eea9eea4cc012b4aa524 Mon Sep 17 00:00:00 2001 From: Misko Hevery Date: Wed, 14 Dec 2011 02:55:31 +0100 Subject: docs(compiler): update the compiler docs --- docs/content/guide/dev_guide.overview.ngdoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/content/guide/dev_guide.overview.ngdoc') diff --git a/docs/content/guide/dev_guide.overview.ngdoc b/docs/content/guide/dev_guide.overview.ngdoc index faf40af5..7f156f72 100644 --- a/docs/content/guide/dev_guide.overview.ngdoc +++ b/docs/content/guide/dev_guide.overview.ngdoc @@ -101,7 +101,7 @@ These input widgets look normal enough, but consider these points: * When this page loaded, angular bound the names of the input widgets (`qty` and `cost`) to variables of the same name. Think of those variables as the "Model" component of the Model-View-Controller design pattern. -* Note the angular/HTML widget, {@link api/angular.widget.input input}. +* Note the angular/HTML widget, {@link api/angular.module.ng.$compileProvider.directive.input input}. You may have noticed that when you enter invalid data or leave the the input fields blank, the borders turn red color, and the display value disappears. These widgets make it easier to implement field validation than coding them in JavaScript, @@ -113,7 +113,7 @@ And finally, the mysterious `{{ double curly braces }}`: This notation, `{{ _expression_ }}`, is a bit of built-in angular {@link dev_guide.compiler.markup markup}, a shortcut for displaying data to the user. The expression within curly braces gets -transformed by the angular compiler into an angular directive ({@link api/angular.directive.ng:bind +transformed by the angular compiler into an angular directive ({@link api/angular.module.ng.$compileProvider.directive.ng:bind ng:bind}). The expression itself can be a combination of both an expression and a {@link dev_guide.templates.filters filter}: `{{ expression | filter }}`. Angular provides filters for formatting display data. -- cgit v1.2.3