{ "id": "guide/template-expression-operators", "title": "Template expression operators", "contents": "\n\n\n
To ensure that you have the best experience possible, this topic is marked for archiving until we determine that it clearly conveys the most accurate information possible.
\nIn the meantime, this topic might be helpful: Hierarchical injectors.
\nIf you think this content should not be archived, please file a GitHub issue.
\nThe Angular template expression language employs a subset of JavaScript syntax supplemented with a few special operators\nfor specific scenarios.
\nSee the
! )linkWhen you use TypeScript's --strictNullChecks flag, you can prevent the type checker from throwing an error with Angular's non-null assertion operator, !.
The Angular non-null assertion operator causes the TypeScript type checker to suspend strict null and undefined checks for a specific property expression.
For example, you can assert that item properties are also defined.
Often, you want to make sure that any property bindings aren't null or undefined.\nHowever, there are situations in which such states are acceptable.\nFor those situations, you can use Angular's non-null assertion operator to prevent TypeScript from reporting that a property is null or undefined.
The non-null assertion operator, !, is optional unless you turn on strict null checks.
For more information, see TypeScript's strict null checking.
\n\n$any() type cast functionlinkSometimes a binding expression triggers a type error during AOT compilation and it is not possible or difficult to fully specify the type.\nTo silence the error, you can use the $any() cast function to cast\nthe expression to the any type as in the following example:
Using $any() prevents TypeScript from reporting that bestByDate is not a member of the item object.
The $any() cast function also works with this to allow access to undeclared members of the component.
The $any() cast function works anywhere in a binding expression where a method call is valid.