diff options
Diffstat (limited to 'docs/content/error/$parse')
| -rw-r--r-- | docs/content/error/$parse/isecdom.ngdoc | 16 | ||||
| -rw-r--r-- | docs/content/error/$parse/isecfld.ngdoc | 18 | ||||
| -rw-r--r-- | docs/content/error/$parse/isecfn.ngdoc | 10 | ||||
| -rw-r--r-- | docs/content/error/$parse/isecwindow.ngdoc | 16 | ||||
| -rw-r--r-- | docs/content/error/$parse/lexerr.ngdoc | 10 | ||||
| -rw-r--r-- | docs/content/error/$parse/syntax.ngdoc | 9 | ||||
| -rw-r--r-- | docs/content/error/$parse/ueoe.ngdoc | 9 |
7 files changed, 88 insertions, 0 deletions
diff --git a/docs/content/error/$parse/isecdom.ngdoc b/docs/content/error/$parse/isecdom.ngdoc new file mode 100644 index 00000000..666bf36c --- /dev/null +++ b/docs/content/error/$parse/isecdom.ngdoc @@ -0,0 +1,16 @@ +@ngdoc error +@name $parse:isecdom +@fullName Referencing a DOM node in Expression +@description + +Occurs when an expression attempts to access a DOM node. + +AngularJS restricts access to DOM nodes from within expressions since it's a known way to +execute arbitrary Javascript code. + +This check is only performed on object index and function calls in Angular expressions. These are +places that are harder for the developer to guard. Dotted member access (such as a.b.c) does not +perform this check - it's up to the developer to not expose such sensitive and powerful objects +directly on the scope chain. + +To resolve this error, avoid access to DOM nodes. diff --git a/docs/content/error/$parse/isecfld.ngdoc b/docs/content/error/$parse/isecfld.ngdoc new file mode 100644 index 00000000..f9acc19d --- /dev/null +++ b/docs/content/error/$parse/isecfld.ngdoc @@ -0,0 +1,18 @@ +@ngdoc error +@name $parse:isecfld +@fullName Referencing 'constructor' Field in Expression +@description + +Occurs when an expression attempts to access an objects constructor field. + +AngularJS bans constructor access from within expressions since constructor +access is a known way to execute arbitrary Javascript code. + +To resolve this error, avoid constructor access. As a last resort, alias +the constructor and access it through the alias instead. + +Example expression that would result in this error: + +``` +<div>{{user.constructor.name}}</div> +``` diff --git a/docs/content/error/$parse/isecfn.ngdoc b/docs/content/error/$parse/isecfn.ngdoc new file mode 100644 index 00000000..417551cb --- /dev/null +++ b/docs/content/error/$parse/isecfn.ngdoc @@ -0,0 +1,10 @@ +@ngdoc error +@name $parse:isecfn +@fullName Referencing Function Disallowed +@description + +Occurs when an expression attempts to access the 'Function' object (constructor for all functions in JavaScript). + +Angular bans access to Function from within expressions since constructor access is a known way to execute arbitrary Javascript code. + +To resolve this error, avoid Function access. diff --git a/docs/content/error/$parse/isecwindow.ngdoc b/docs/content/error/$parse/isecwindow.ngdoc new file mode 100644 index 00000000..81adeea0 --- /dev/null +++ b/docs/content/error/$parse/isecwindow.ngdoc @@ -0,0 +1,16 @@ +@ngdoc error +@name $parse:isecwindow +@fullName Referencing Window object in Expression +@description + +Occurs when an expression attempts to access a Window object. + +AngularJS restricts access to the Window object from within expressions since it's a known way to +execute arbitrary Javascript code. + +This check is only performed on object index and function calls in Angular expressions. These are +places that are harder for the developer to guard. Dotted member access (such as a.b.c) does not +perform this check - it's up to the developer to not expose such sensitive and powerful objects +directly on the scope chain. + +To resolve this error, avoid Window access. diff --git a/docs/content/error/$parse/lexerr.ngdoc b/docs/content/error/$parse/lexerr.ngdoc new file mode 100644 index 00000000..2a40d939 --- /dev/null +++ b/docs/content/error/$parse/lexerr.ngdoc @@ -0,0 +1,10 @@ +@ngdoc error +@name $parse:lexerr +@fullName Lexer Error +@description + +Occurs when an expression has a lexical error, for example a malformed number (0.5e-) or an invalid unicode escape. + +The error message contains a more precise error. + +To resolve, learn more about {@link guide/expression Angular expressions}, identify the error and fix the expression's syntax. diff --git a/docs/content/error/$parse/syntax.ngdoc b/docs/content/error/$parse/syntax.ngdoc new file mode 100644 index 00000000..1af212f1 --- /dev/null +++ b/docs/content/error/$parse/syntax.ngdoc @@ -0,0 +1,9 @@ +@ngdoc error +@name $parse:syntax +@fullName Syntax Error +@description + +Occurs when there is a syntax error in an expression. These errors are thrown while compiling the expression. +The error message contains a more precise description of the error, including the location (column) in the expression where the error occurred. + +To resolve, learn more about {@link guide/expression Angular expressions}, identify the error and fix the expression's syntax. diff --git a/docs/content/error/$parse/ueoe.ngdoc b/docs/content/error/$parse/ueoe.ngdoc new file mode 100644 index 00000000..97535a31 --- /dev/null +++ b/docs/content/error/$parse/ueoe.ngdoc @@ -0,0 +1,9 @@ +@ngdoc error +@name $parse:ueoe +@fullName Unexpected End of Expression +@description + +Occurs when an expression is missing tokens at the end of the expression. +For example, forgetting a closing bracket in an expression will trigger this error. + +To resolve, learn more about {@link guide/expression Angular expressions}, identify the error and fix the expression's syntax. |