aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content/error/parse
diff options
context:
space:
mode:
Diffstat (limited to 'docs/content/error/parse')
-rw-r--r--docs/content/error/parse/isecdom.ngdoc16
-rw-r--r--docs/content/error/parse/isecfld.ngdoc18
-rw-r--r--docs/content/error/parse/isecfn.ngdoc10
-rw-r--r--docs/content/error/parse/isecwindow.ngdoc16
-rw-r--r--docs/content/error/parse/lexerr.ngdoc10
-rw-r--r--docs/content/error/parse/syntax.ngdoc9
-rw-r--r--docs/content/error/parse/ueoe.ngdoc9
7 files changed, 0 insertions, 88 deletions
diff --git a/docs/content/error/parse/isecdom.ngdoc b/docs/content/error/parse/isecdom.ngdoc
deleted file mode 100644
index 666bf36c..00000000
--- a/docs/content/error/parse/isecdom.ngdoc
+++ /dev/null
@@ -1,16 +0,0 @@
-@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
deleted file mode 100644
index f9acc19d..00000000
--- a/docs/content/error/parse/isecfld.ngdoc
+++ /dev/null
@@ -1,18 +0,0 @@
-@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
deleted file mode 100644
index 417551cb..00000000
--- a/docs/content/error/parse/isecfn.ngdoc
+++ /dev/null
@@ -1,10 +0,0 @@
-@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
deleted file mode 100644
index 81adeea0..00000000
--- a/docs/content/error/parse/isecwindow.ngdoc
+++ /dev/null
@@ -1,16 +0,0 @@
-@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
deleted file mode 100644
index 2a40d939..00000000
--- a/docs/content/error/parse/lexerr.ngdoc
+++ /dev/null
@@ -1,10 +0,0 @@
-@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
deleted file mode 100644
index 1af212f1..00000000
--- a/docs/content/error/parse/syntax.ngdoc
+++ /dev/null
@@ -1,9 +0,0 @@
-@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
deleted file mode 100644
index 97535a31..00000000
--- a/docs/content/error/parse/ueoe.ngdoc
+++ /dev/null
@@ -1,9 +0,0 @@
-@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.