fix(template syntax): minor fixes

closes #535
This commit is contained in:
Victor Berchet 2015-12-15 14:10:10 -08:00 committed by Ward Bell
parent a89e57f1b1
commit 933433ceea
1 changed files with 78 additions and 82 deletions

View File

@ -330,10 +330,6 @@ table
+makeExample('template-syntax/ts/app/app.component.html', 'style-binding-syntax-1')(format=".") +makeExample('template-syntax/ts/app/app.component.html', 'style-binding-syntax-1')(format=".")
</div> </div>
.l-sub-section
:marked
According to this rule, we should write `[inner-h-t-m-l]` to access the elements `innerHTML` property.
Fortunately, the Angular template parser recognizes `inner-html` as an acceptable alias for `innerHTML`.
:marked :marked
Lets descend from the architectural clouds and look at each of these binding types in concrete detail. Lets descend from the architectural clouds and look at each of these binding types in concrete detail.
@ -659,7 +655,7 @@ code-example(format="", language="html").
We can write our own two-way binding directive that follows this pattern if we're ever in the mood to do so. We can write our own two-way binding directive that follows this pattern if we're ever in the mood to do so.
:marked :marked
Is `[{ngModel}]` all we need? Is there ever a reason to fall back to its expanded form? Is `[(ngModel)]` all we need? Is there ever a reason to fall back to its expanded form?
Well `NgModel` can only set the target property. Well `NgModel` can only set the target property.
What if we need to do something more or something different when the user changes the value? What if we need to do something more or something different when the user changes the value?