docs(guide/filters): clarify when filters are executed #14758
Conversation
|
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
1 similar comment
|
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
Narretz
force-pushed
the
docs-filter-input
branch
from
f48a349 to
b78e210
Compare
|
CLAs look good, thanks! |
1 similar comment
|
CLAs look good, thanks! |
| @@ -31,6 +31,16 @@ Filters may have arguments. The syntax for this is | |||
| E.g. the markup `{{ 1234 | number:2 }}` formats the number 1234 with 2 decimal points using the | |||
| {@link ng.filter:number `number`} filter. The resulting value is `1,234.00`. | |||
|
|
|||
| ### When filters are executed | |||
|
|
|||
| In templates, filters are only executed when their inputs have changed. This is more performant than executing | |||
There was a problem hiding this comment.
I would clarify that this only applies to stateless filters (the default kind). Filters marked as stateful are called on every digest.
There was a problem hiding this comment.
Yes, I should mention this for completeness
Narretz
force-pushed
the
docs-filter-input
branch
from
9f634b9 to
5b8a290
Compare
|
LGTM |
No description provided.