From 33e1bdc543bcb7875dcc004d487333393670ed2d Mon Sep 17 00:00:00 2001 From: Peter Bacon Darwin Date: Sun, 16 Feb 2014 22:02:31 +0000 Subject: chore(errors): rename folders to match namespaces --- docs/content/error/$animate/notcsel.ngdoc | 6 +++ docs/content/error/$cacheFactory/iid.ngdoc | 8 +++ docs/content/error/$compile/ctreq.ngdoc | 49 +++++++++++++++++ docs/content/error/$compile/iscp.ngdoc | 25 +++++++++ docs/content/error/$compile/multidir.ngdoc | 17 ++++++ docs/content/error/$compile/nodomevents.ngdoc | 20 +++++++ docs/content/error/$compile/nonassign.ngdoc | 41 ++++++++++++++ docs/content/error/$compile/selmulti.ngdoc | 20 +++++++ docs/content/error/$compile/tpload.ngdoc | 11 ++++ docs/content/error/$compile/tplrt.ngdoc | 39 ++++++++++++++ docs/content/error/$compile/uterdir.ngdoc | 34 ++++++++++++ docs/content/error/$controller/noscp.ngdoc | 21 ++++++++ docs/content/error/$httpBackend/noxhr.ngdoc | 10 ++++ docs/content/error/$injector/cdep.ngdoc | 26 +++++++++ docs/content/error/$injector/itkn.ngdoc | 26 +++++++++ docs/content/error/$injector/modulerr.ngdoc | 11 ++++ docs/content/error/$injector/nomod.ngdoc | 26 +++++++++ docs/content/error/$injector/pget.ngdoc | 26 +++++++++ docs/content/error/$injector/unpr.ngdoc | 26 +++++++++ docs/content/error/$interpolate/interr.ngdoc | 7 +++ docs/content/error/$interpolate/noconcat.ngdoc | 12 +++++ docs/content/error/$location/ihshprfx.ngdoc | 17 ++++++ docs/content/error/$location/ipthprfx.ngdoc | 8 +++ docs/content/error/$location/isrcharg.ngdoc | 9 ++++ docs/content/error/$parse/isecdom.ngdoc | 16 ++++++ docs/content/error/$parse/isecfld.ngdoc | 18 +++++++ docs/content/error/$parse/isecfn.ngdoc | 10 ++++ docs/content/error/$parse/isecwindow.ngdoc | 16 ++++++ docs/content/error/$parse/lexerr.ngdoc | 10 ++++ docs/content/error/$parse/syntax.ngdoc | 9 ++++ docs/content/error/$parse/ueoe.ngdoc | 9 ++++ docs/content/error/$resource/badargs.ngdoc | 9 ++++ docs/content/error/$resource/badcfg.ngdoc | 11 ++++ docs/content/error/$resource/badmember.ngdoc | 27 ++++++++++ docs/content/error/$resource/badname.ngdoc | 8 +++ docs/content/error/$rootScope/infdig.ngdoc | 17 ++++++ docs/content/error/$rootScope/inprog.ngdoc | 74 ++++++++++++++++++++++++++ docs/content/error/$sanitize/badparse.ngdoc | 11 ++++ docs/content/error/$sce/icontext.ngdoc | 8 +++ docs/content/error/$sce/iequirks.ngdoc | 17 ++++++ docs/content/error/$sce/imatcher.ngdoc | 9 ++++ docs/content/error/$sce/insecurl.ngdoc | 26 +++++++++ docs/content/error/$sce/itype.ngdoc | 8 +++ docs/content/error/$sce/iwcard.ngdoc | 9 ++++ docs/content/error/$sce/unsafe.ngdoc | 15 ++++++ docs/content/error/animate/notcsel.ngdoc | 6 --- docs/content/error/cacheFactory/iid.ngdoc | 8 --- docs/content/error/compile/ctreq.ngdoc | 49 ----------------- docs/content/error/compile/iscp.ngdoc | 25 --------- docs/content/error/compile/multidir.ngdoc | 17 ------ docs/content/error/compile/nodomevents.ngdoc | 20 ------- docs/content/error/compile/nonassign.ngdoc | 41 -------------- docs/content/error/compile/selmulti.ngdoc | 20 ------- docs/content/error/compile/tpload.ngdoc | 11 ---- docs/content/error/compile/tplrt.ngdoc | 39 -------------- docs/content/error/compile/uterdir.ngdoc | 34 ------------ docs/content/error/controller/noscp.ngdoc | 21 -------- docs/content/error/httpBackend/noxhr.ngdoc | 10 ---- docs/content/error/injector/cdep.ngdoc | 26 --------- docs/content/error/injector/itkn.ngdoc | 26 --------- docs/content/error/injector/modulerr.ngdoc | 11 ---- docs/content/error/injector/nomod.ngdoc | 26 --------- docs/content/error/injector/pget.ngdoc | 26 --------- docs/content/error/injector/unpr.ngdoc | 26 --------- docs/content/error/interpolate/interr.ngdoc | 7 --- docs/content/error/interpolate/noconcat.ngdoc | 12 ----- docs/content/error/location/ihshprfx.ngdoc | 17 ------ docs/content/error/location/ipthprfx.ngdoc | 8 --- docs/content/error/location/isrcharg.ngdoc | 9 ---- docs/content/error/parse/isecdom.ngdoc | 16 ------ docs/content/error/parse/isecfld.ngdoc | 18 ------- docs/content/error/parse/isecfn.ngdoc | 10 ---- docs/content/error/parse/isecwindow.ngdoc | 16 ------ docs/content/error/parse/lexerr.ngdoc | 10 ---- docs/content/error/parse/syntax.ngdoc | 9 ---- docs/content/error/parse/ueoe.ngdoc | 9 ---- docs/content/error/resource/badargs.ngdoc | 9 ---- docs/content/error/resource/badcfg.ngdoc | 11 ---- docs/content/error/resource/badmember.ngdoc | 27 ---------- docs/content/error/resource/badname.ngdoc | 8 --- docs/content/error/rootScope/infdig.ngdoc | 17 ------ docs/content/error/rootScope/inprog.ngdoc | 74 -------------------------- docs/content/error/sanitize/badparse.ngdoc | 11 ---- docs/content/error/sce/icontext.ngdoc | 8 --- docs/content/error/sce/iequirks.ngdoc | 17 ------ docs/content/error/sce/imatcher.ngdoc | 9 ---- docs/content/error/sce/insecurl.ngdoc | 26 --------- docs/content/error/sce/itype.ngdoc | 8 --- docs/content/error/sce/iwcard.ngdoc | 9 ---- docs/content/error/sce/unsafe.ngdoc | 15 ------ 90 files changed, 832 insertions(+), 832 deletions(-) create mode 100644 docs/content/error/$animate/notcsel.ngdoc create mode 100644 docs/content/error/$cacheFactory/iid.ngdoc create mode 100644 docs/content/error/$compile/ctreq.ngdoc create mode 100644 docs/content/error/$compile/iscp.ngdoc create mode 100644 docs/content/error/$compile/multidir.ngdoc create mode 100644 docs/content/error/$compile/nodomevents.ngdoc create mode 100644 docs/content/error/$compile/nonassign.ngdoc create mode 100644 docs/content/error/$compile/selmulti.ngdoc create mode 100644 docs/content/error/$compile/tpload.ngdoc create mode 100644 docs/content/error/$compile/tplrt.ngdoc create mode 100644 docs/content/error/$compile/uterdir.ngdoc create mode 100644 docs/content/error/$controller/noscp.ngdoc create mode 100644 docs/content/error/$httpBackend/noxhr.ngdoc create mode 100644 docs/content/error/$injector/cdep.ngdoc create mode 100644 docs/content/error/$injector/itkn.ngdoc create mode 100644 docs/content/error/$injector/modulerr.ngdoc create mode 100644 docs/content/error/$injector/nomod.ngdoc create mode 100644 docs/content/error/$injector/pget.ngdoc create mode 100644 docs/content/error/$injector/unpr.ngdoc create mode 100644 docs/content/error/$interpolate/interr.ngdoc create mode 100644 docs/content/error/$interpolate/noconcat.ngdoc create mode 100644 docs/content/error/$location/ihshprfx.ngdoc create mode 100644 docs/content/error/$location/ipthprfx.ngdoc create mode 100644 docs/content/error/$location/isrcharg.ngdoc create mode 100644 docs/content/error/$parse/isecdom.ngdoc create mode 100644 docs/content/error/$parse/isecfld.ngdoc create mode 100644 docs/content/error/$parse/isecfn.ngdoc create mode 100644 docs/content/error/$parse/isecwindow.ngdoc create mode 100644 docs/content/error/$parse/lexerr.ngdoc create mode 100644 docs/content/error/$parse/syntax.ngdoc create mode 100644 docs/content/error/$parse/ueoe.ngdoc create mode 100644 docs/content/error/$resource/badargs.ngdoc create mode 100644 docs/content/error/$resource/badcfg.ngdoc create mode 100644 docs/content/error/$resource/badmember.ngdoc create mode 100644 docs/content/error/$resource/badname.ngdoc create mode 100644 docs/content/error/$rootScope/infdig.ngdoc create mode 100644 docs/content/error/$rootScope/inprog.ngdoc create mode 100644 docs/content/error/$sanitize/badparse.ngdoc create mode 100644 docs/content/error/$sce/icontext.ngdoc create mode 100644 docs/content/error/$sce/iequirks.ngdoc create mode 100644 docs/content/error/$sce/imatcher.ngdoc create mode 100644 docs/content/error/$sce/insecurl.ngdoc create mode 100644 docs/content/error/$sce/itype.ngdoc create mode 100644 docs/content/error/$sce/iwcard.ngdoc create mode 100644 docs/content/error/$sce/unsafe.ngdoc delete mode 100644 docs/content/error/animate/notcsel.ngdoc delete mode 100644 docs/content/error/cacheFactory/iid.ngdoc delete mode 100644 docs/content/error/compile/ctreq.ngdoc delete mode 100644 docs/content/error/compile/iscp.ngdoc delete mode 100644 docs/content/error/compile/multidir.ngdoc delete mode 100644 docs/content/error/compile/nodomevents.ngdoc delete mode 100644 docs/content/error/compile/nonassign.ngdoc delete mode 100644 docs/content/error/compile/selmulti.ngdoc delete mode 100644 docs/content/error/compile/tpload.ngdoc delete mode 100644 docs/content/error/compile/tplrt.ngdoc delete mode 100644 docs/content/error/compile/uterdir.ngdoc delete mode 100644 docs/content/error/controller/noscp.ngdoc delete mode 100644 docs/content/error/httpBackend/noxhr.ngdoc delete mode 100644 docs/content/error/injector/cdep.ngdoc delete mode 100644 docs/content/error/injector/itkn.ngdoc delete mode 100644 docs/content/error/injector/modulerr.ngdoc delete mode 100644 docs/content/error/injector/nomod.ngdoc delete mode 100644 docs/content/error/injector/pget.ngdoc delete mode 100644 docs/content/error/injector/unpr.ngdoc delete mode 100644 docs/content/error/interpolate/interr.ngdoc delete mode 100644 docs/content/error/interpolate/noconcat.ngdoc delete mode 100644 docs/content/error/location/ihshprfx.ngdoc delete mode 100644 docs/content/error/location/ipthprfx.ngdoc delete mode 100644 docs/content/error/location/isrcharg.ngdoc delete mode 100644 docs/content/error/parse/isecdom.ngdoc delete mode 100644 docs/content/error/parse/isecfld.ngdoc delete mode 100644 docs/content/error/parse/isecfn.ngdoc delete mode 100644 docs/content/error/parse/isecwindow.ngdoc delete mode 100644 docs/content/error/parse/lexerr.ngdoc delete mode 100644 docs/content/error/parse/syntax.ngdoc delete mode 100644 docs/content/error/parse/ueoe.ngdoc delete mode 100644 docs/content/error/resource/badargs.ngdoc delete mode 100644 docs/content/error/resource/badcfg.ngdoc delete mode 100644 docs/content/error/resource/badmember.ngdoc delete mode 100644 docs/content/error/resource/badname.ngdoc delete mode 100644 docs/content/error/rootScope/infdig.ngdoc delete mode 100644 docs/content/error/rootScope/inprog.ngdoc delete mode 100644 docs/content/error/sanitize/badparse.ngdoc delete mode 100644 docs/content/error/sce/icontext.ngdoc delete mode 100644 docs/content/error/sce/iequirks.ngdoc delete mode 100644 docs/content/error/sce/imatcher.ngdoc delete mode 100644 docs/content/error/sce/insecurl.ngdoc delete mode 100644 docs/content/error/sce/itype.ngdoc delete mode 100644 docs/content/error/sce/iwcard.ngdoc delete mode 100644 docs/content/error/sce/unsafe.ngdoc (limited to 'docs/content') diff --git a/docs/content/error/$animate/notcsel.ngdoc b/docs/content/error/$animate/notcsel.ngdoc new file mode 100644 index 00000000..d8ceaa0e --- /dev/null +++ b/docs/content/error/$animate/notcsel.ngdoc @@ -0,0 +1,6 @@ +@ngdoc error +@name $animate:notcsel +@fullName Not class CSS selector +@description + +Expecting a CSS selector for class. Class selectors must start with `.`, for example: `.my-class-name`. diff --git a/docs/content/error/$cacheFactory/iid.ngdoc b/docs/content/error/$cacheFactory/iid.ngdoc new file mode 100644 index 00000000..62e985e8 --- /dev/null +++ b/docs/content/error/$cacheFactory/iid.ngdoc @@ -0,0 +1,8 @@ +@ngdoc error +@name $cacheFactory:iid +@fullName Invalid ID +@description + +This error occurs when trying to create a new `cache` object via {@link ng.$cacheFactory} with an ID that was already used to create another cache object. + +To resolve the error please use a different cache ID when calling `$cacheFactory`. diff --git a/docs/content/error/$compile/ctreq.ngdoc b/docs/content/error/$compile/ctreq.ngdoc new file mode 100644 index 00000000..47c876a3 --- /dev/null +++ b/docs/content/error/$compile/ctreq.ngdoc @@ -0,0 +1,49 @@ +@ngdoc error +@name $compile:ctreq +@fullName Missing Required Controller +@description + +This error occurs when {@link ng.$compile HTML compiler} tries to process a directive that specifies the {@link ng.$compile#description_comprehensive-directive-api_directive-definition-object `require` option} in a {@link ng.$compile#description_comprehensive-directive-api directive definition}, +but the required directive controller is not present on the current DOM element (or its ancestor element, if `^` was specified). + +To resolve this error ensure that there is no typo in the required controller name and that the required directive controller is present on the current element. + +If the required controller is expected to be on a ancestor element, make ensure that you prefix the controller name in the `require` definition with `^`. + +If the required controller is optionally requested, use `?` or `^?` to specify that. + + +Example of a directive that requires {@link ng.directive:ngModel ngModel} controller: +``` +myApp.directive('myDirective', function() { + return { + require: 'ngModel', + ... + } +} +``` + +This directive can then be used as: +``` + +``` + + +Example of a directive that optionally requires a {@link ng.directive:form form} controller from an ancestor: +``` +myApp.directive('myDirective', function() { + return { + require: '^?form', + ... + } +} +``` + +This directive can then be used as: +``` +
+
+ +
+
+``` diff --git a/docs/content/error/$compile/iscp.ngdoc b/docs/content/error/$compile/iscp.ngdoc new file mode 100644 index 00000000..1450dec9 --- /dev/null +++ b/docs/content/error/$compile/iscp.ngdoc @@ -0,0 +1,25 @@ +@ngdoc error +@name $compile:iscp +@fullName Invalid Isolate Scope Definition +@description + +When declaring isolate scope the scope definition object must be in specific format which starts with mode character (`@&=`) with an optional local name. + +``` +myModule.directive('directiveName', function factory() { + return { + ... + scope: { + 'attrName': '@', // OK + 'attrName2': '=localName', // OK + 'attrName3': 'name', // ERROR: missing mode @&= + 'attrName4': ' = name', // ERROR: extra spaces + 'attrName5': 'name=', // ERROR: must be prefixed with @&= + } + ... + } +}); +``` + +Please refer to the {@link ng.$compile#description_comprehensive-directive-api_directive-definition-object +`scope` option} of the directive definition documentation to learn more about the API. diff --git a/docs/content/error/$compile/multidir.ngdoc b/docs/content/error/$compile/multidir.ngdoc new file mode 100644 index 00000000..439d82c7 --- /dev/null +++ b/docs/content/error/$compile/multidir.ngdoc @@ -0,0 +1,17 @@ +@ngdoc error +@name $compile:multidir +@fullName Multiple Directive Resource Contention +@description + +This error occurs when multiple directives are applied to the same DOM element, and +processing them would result in a collision or an unsupported configuration. + + +To resolve this issue remove one of the directives which is causing the collision. + +Example scenarios of multiple incompatible directives applied to the same element include: + +* Multiple directives requesting `isolated scope`. +* Multiple directives publishing a controller under the same name. +* Multiple directives declared with the `transclusion` option. +* Multiple directives attempting to define a `template` or `templateURL`. diff --git a/docs/content/error/$compile/nodomevents.ngdoc b/docs/content/error/$compile/nodomevents.ngdoc new file mode 100644 index 00000000..ed1888c7 --- /dev/null +++ b/docs/content/error/$compile/nodomevents.ngdoc @@ -0,0 +1,20 @@ +@ngdoc error +@name $compile:nodomevents +@fullName Interpolated Event Attributes +@description + +This error occurs when one tries to create a binding for event handler attributes like `onclick`, `onload`, `onsubmit`, etc. + +There is no practical value in binding to these attributes and doing so only exposes your application to security vulnerabilities like XSS. +For these reasons binding to event handler attributes (all attributes that start with `on` and `formaction` attribute) is not supported. + + +An example code that would allow XSS vulnerability by evaluating user input in the window context could look like this: +``` + +
click me
+``` + +Since the `onclick` evaluates the value as JavaScript code in the window context, setting the `username` model to a value like `javascript:alert('PWND')` would result in script injection when the `div` is clicked. + + diff --git a/docs/content/error/$compile/nonassign.ngdoc b/docs/content/error/$compile/nonassign.ngdoc new file mode 100644 index 00000000..3a7d996b --- /dev/null +++ b/docs/content/error/$compile/nonassign.ngdoc @@ -0,0 +1,41 @@ +@ngdoc error +@name $compile:nonassign +@fullName Non-Assignable Expression +@description + +This error occurs when a directive defines an isolate scope property +(using the `=` mode in the {@link ng.$compile#description_comprehensive-directive-api_directive-definition-object +`scope` option} of a directive definition) but the directive is used with an expression that is not-assignable. + +In order for the two-way data-binding to work, it must be possible to write new values back into the path defined with the expression. + +For example, given a directive: + +``` +myModule.directive('myDirective', function factory() { + return { + ... + scope: { + 'bind': '=localValue' + } + ... + } +}); +``` + +Following are invalid uses of this directive: +``` + + + + + +``` + + +To resolve this error, always use path expressions with scope properties that are two-way data-bound: +``` + + +``` + diff --git a/docs/content/error/$compile/selmulti.ngdoc b/docs/content/error/$compile/selmulti.ngdoc new file mode 100644 index 00000000..51221ad8 --- /dev/null +++ b/docs/content/error/$compile/selmulti.ngdoc @@ -0,0 +1,20 @@ +@ngdoc error +@name $compile:selmulti +@fullName Binding to Multiple Attribute +@description + +Binding to the `multiple` attribute of `select` element is not supported since switching between multiple and single mode changes the {@link ng.directive:ngModel `ngModel`} object type from instance to array of instances which breaks the model semantics. + +If you need to use different types of `select` elements in your template based on some variable, please use {@link ng.directive:ngIf ngIf} or {@link ng.directive:ngSwitch ngSwitch} directives to select one of them to be used at runtime. + + +Example with invalid usage: +``` + +``` + +Example that uses ngIf to pick one of the `select` elements based on a variable: +``` + + +``` diff --git a/docs/content/error/$compile/tpload.ngdoc b/docs/content/error/$compile/tpload.ngdoc new file mode 100644 index 00000000..b2b4fb2d --- /dev/null +++ b/docs/content/error/$compile/tpload.ngdoc @@ -0,0 +1,11 @@ +@ngdoc error +@name $compile:tpload +@fullName Error Loading Template +@description + +This error occurs when {@link ng.$compile `$compile`} attempts to fetch a template from some URL, and the request fails. + +To resolve this error, ensure that the URL of the template is spelled correctly and resolves to correct absolute URL. +The [Chrome Developer Tools](https://developers.google.com/chrome-developer-tools/docs/network#network_panel_overview) might also be helpful in determining why the request failed. + +If you are using {@link ng.$templateCache} to pre-load templates, ensure that the cache was populated with the template. diff --git a/docs/content/error/$compile/tplrt.ngdoc b/docs/content/error/$compile/tplrt.ngdoc new file mode 100644 index 00000000..3c29dbdc --- /dev/null +++ b/docs/content/error/$compile/tplrt.ngdoc @@ -0,0 +1,39 @@ +@ngdoc error +@name $compile:tplrt +@fullName Invalid Template Root +@description + +When a directive is declared with `template` (or `templateUrl`) and `replace` mode on, the template +must have exactly one root element. That is, the text of the template property or the content +referenced by the templateUrl must be contained within a single html element. +For example, `

blah blah blah

` instead of simply `blah blah blah`. +Otherwise, the replacement operation would result in a single element (the directive) being replaced +with multiple elements or nodes, which is unsupported and not commonly needed in practice. + + +For example a directive with definition: + +``` +myModule.directive('myDirective', function factory() { + return { + ... + replace: true, + templateUrl: 'someUrl' + ... + } +}); +``` + +And a template provided at URL `someUrl`. The template must be an html fragment that has only a +single root element, like the `div` element in this template: + +``` +
Hello World!
+``` + +An an invalid template to be used with this directive is one that defines multiple root nodes or +elements. For example: + +``` +Hello World! +``` diff --git a/docs/content/error/$compile/uterdir.ngdoc b/docs/content/error/$compile/uterdir.ngdoc new file mode 100644 index 00000000..c1f263f9 --- /dev/null +++ b/docs/content/error/$compile/uterdir.ngdoc @@ -0,0 +1,34 @@ +@ngdoc error +@name $compile:uterdir +@fullName Unterminated Directive +@description + +This error occurs when using multi-element directives and a `directive-start` attribute fails to form a matching pair with a corresponding `directive-end` attribute. +A `directive-start` should have a matching `directive-end` on a sibling node in the DOM. For instance, + +``` + + I get repeated + I also get repeated +
+``` + +is a valid example. + +This error can occur in several different ways. One is by leaving out the `directive-end` attribute, like so: + +``` +
+ +
+``` + +Another is by nesting a `directive-end` inside of `directive-start`, or vice versa: + +``` +
+ +
+``` + +To avoid this error, make sure each `directive-start` you use has a matching `directive-end` on a sibling node in the DOM. diff --git a/docs/content/error/$controller/noscp.ngdoc b/docs/content/error/$controller/noscp.ngdoc new file mode 100644 index 00000000..26257546 --- /dev/null +++ b/docs/content/error/$controller/noscp.ngdoc @@ -0,0 +1,21 @@ +@ngdoc error +@name $controller:noscp +@fullName Missing $scope object +@description + +This error occurs when {@link ng.$controller $controller} service is called in order to instantiate a new controller but no scope is provided via `$scope` property of the locals map. + +Example of incorrect usage that leads to this error: +``` +$controller(MyController); +//or +$controller(MyController, {scope: newScope}); +``` + +To fix the example above please provide a scope to the $controller call: + +``` +$controller(MyController, {$scope, newScope}); +``` + +Please consult the {@link ng.$controller $controller} service api docs to learn more. diff --git a/docs/content/error/$httpBackend/noxhr.ngdoc b/docs/content/error/$httpBackend/noxhr.ngdoc new file mode 100644 index 00000000..e2d5901d --- /dev/null +++ b/docs/content/error/$httpBackend/noxhr.ngdoc @@ -0,0 +1,10 @@ +@ngdoc error +@name $httpBackend:noxhr +@fullName Unsupported XHR +@description + +This error occurs in browsers that do not support XmlHttpRequest. AngularJS +supports Safari, Chrome, Firefox, Opera, IE8 and higher, and mobile browsers +(Android, Chrome Mobile, iOS Safari). To avoid this error, use an officially +supported browser. + diff --git a/docs/content/error/$injector/cdep.ngdoc b/docs/content/error/$injector/cdep.ngdoc new file mode 100644 index 00000000..0e6526b8 --- /dev/null +++ b/docs/content/error/$injector/cdep.ngdoc @@ -0,0 +1,26 @@ +@ngdoc error +@name $injector:cdep +@fullName Circular Dependency +@description + +This error occurs when the {@link angular.injector $injector} tries to get +a service that depends on itself, either directly or indirectly. To fix this, +construct your dependency chain such that there are no circular dependencies. + +For example: + +``` +angular.module('myApp', []) + .factory('myService', function (myService) { + // ... + }) + .controller('MyCtrl', function ($scope, myService) { + // ... + }); +``` + +When an instance of `MyCtrl` is created, the service `myService` will be created +by the `$injector`. `myService` depends on itself, which causes the `$injector` +to detect a circular dependency and throw the error. + +For more information, see the {@link guide/di Dependency Injection Guide}. \ No newline at end of file diff --git a/docs/content/error/$injector/itkn.ngdoc b/docs/content/error/$injector/itkn.ngdoc new file mode 100644 index 00000000..5437dce7 --- /dev/null +++ b/docs/content/error/$injector/itkn.ngdoc @@ -0,0 +1,26 @@ +@ngdoc error +@name $injector:itkn +@fullName Bad Injection Token +@description + +This error occurs when using a bad token as a dependency injection annotation. +Dependency injection annotation tokens should always be strings. Using any other +type will cause this error to be thrown. + +Examples of code with bad injection tokens include: + +``` +var myCtrl = function ($scope, $http) { /* ... */ }; +myCtrl.$inject = ['$scope', 42]; + +myAppModule.controller('MyCtrl', ['$scope', {}, function ($scope, $timeout) { + // ... +}]); +``` + +The bad injection tokens are `42` in the first example and `{}` in the second. +To avoid the error, always use string literals for dependency injection annotation +tokens. + +For an explanation of what injection annotations are and how to use them, refer +to the {@link guide/di Dependency Injection Guide}. \ No newline at end of file diff --git a/docs/content/error/$injector/modulerr.ngdoc b/docs/content/error/$injector/modulerr.ngdoc new file mode 100644 index 00000000..4b92a5de --- /dev/null +++ b/docs/content/error/$injector/modulerr.ngdoc @@ -0,0 +1,11 @@ +@ngdoc error +@name $injector:modulerr +@fullName Module Error +@description + +This error occurs when a module fails to load due to some exception. The error +message above should provide additional context. + +In AngularJS `1.2.0` and later, `ngRoute` has been moved to its own module. +If you are getting this error after upgrading to `1.2.x`, be sure that you've +installed {@link ngRoute `ngRoute`}. diff --git a/docs/content/error/$injector/nomod.ngdoc b/docs/content/error/$injector/nomod.ngdoc new file mode 100644 index 00000000..5f8fb1e6 --- /dev/null +++ b/docs/content/error/$injector/nomod.ngdoc @@ -0,0 +1,26 @@ +@ngdoc error +@name $injector:nomod +@fullName Module Unavailable +@description + +This error occurs when trying to "re-open" a module that has not yet been defined. + +To define a new module, call {@link angular.module angular.module} with a name +and an array of dependent modules, like so: + +``` +// When defining a module with no module dependencies, +// the requires array should be defined and empty. +var myApp = angular.module('myApp', []); +``` + +To retrieve a reference to the same module for further configuration, call +`angular.module` without the `requires` array. + +``` +var myApp = angular.module('myApp'); +``` + +Calling `angular.module` without the `requires` array when the module has not yet +been defined causes this error to be thrown. To fix it, define your module with +a name and an empty array, as in the first example above. \ No newline at end of file diff --git a/docs/content/error/$injector/pget.ngdoc b/docs/content/error/$injector/pget.ngdoc new file mode 100644 index 00000000..1772d348 --- /dev/null +++ b/docs/content/error/$injector/pget.ngdoc @@ -0,0 +1,26 @@ +@ngdoc error +@name $injector:pget +@fullName Provider Missing $get +@description + +This error occurs when attempting to register a provider that does not have a +`$get` method. For example: + +``` +function BadProvider() {} // No $get method! +angular.module("myApp", []) + .provider('bad', BadProvider); // this throws the error +``` + +To fix the error, fill in the `$get` method on the provider like so: + +``` +function GoodProvider() { + this.$get = angular.noop; +} +angular.module("myApp", []) + .provider('good', GoodProvider); +``` + +For more information, refer to the {@link auto.$provide#methods_provider +$provide.provider} api doc. \ No newline at end of file diff --git a/docs/content/error/$injector/unpr.ngdoc b/docs/content/error/$injector/unpr.ngdoc new file mode 100644 index 00000000..1b0faa8e --- /dev/null +++ b/docs/content/error/$injector/unpr.ngdoc @@ -0,0 +1,26 @@ +@ngdoc error +@name $injector:unpr +@fullName Unknown Provider +@description + +This error results from the `$injector` being unable to resolve a required +dependency. To fix this, make sure the dependency is defined and spelled +correctly. For example: + +``` +angular.module('myApp', []) + .controller('myCtrl', ['myService', function (myService) { + // Do something with myService + }]); +``` + +This code will fail with `$injector:unpr` if `myService` is not defined. Making +sure each dependency is defined will fix the problem. + +``` +angular.module('myApp', []) + .service('myService', function () { /* ... */ }) + .controller('myCtrl', ['myService', function (myService) { + // Do something with myService + }]); +``` \ No newline at end of file diff --git a/docs/content/error/$interpolate/interr.ngdoc b/docs/content/error/$interpolate/interr.ngdoc new file mode 100644 index 00000000..8d56c8d0 --- /dev/null +++ b/docs/content/error/$interpolate/interr.ngdoc @@ -0,0 +1,7 @@ +@ngdoc error +@name $interpolate:interr +@fullName Interpolation Error +@description + +This error occurs when interpolation fails due to some exception. The error +message above should provide additional context. diff --git a/docs/content/error/$interpolate/noconcat.ngdoc b/docs/content/error/$interpolate/noconcat.ngdoc new file mode 100644 index 00000000..0853544e --- /dev/null +++ b/docs/content/error/$interpolate/noconcat.ngdoc @@ -0,0 +1,12 @@ +@ngdoc error +@name $interpolate:noconcat +@fullName Multiple Expressions +@description + +This error occurs when performing an interpolation that concatenates multiple +expressions when a trusted value is required. Concatenating expressions makes +it hard to reason about whether some combination of concatenated values are +unsafe to use and could easily lead to XSS. + +For more information about how AngularJS helps keep your app secure, refer to +the {@link ng.$sce $sce} API doc. \ No newline at end of file diff --git a/docs/content/error/$location/ihshprfx.ngdoc b/docs/content/error/$location/ihshprfx.ngdoc new file mode 100644 index 00000000..8acab933 --- /dev/null +++ b/docs/content/error/$location/ihshprfx.ngdoc @@ -0,0 +1,17 @@ +@ngdoc error +@name $location:ihshprfx +@fullName Missing Hash Prefix +@description + +This error occurs when {@link ng.$location $location} service is configured to use a hash prefix but this prefix was not present in a url that the `$location` service was asked to parse. + +For example if you configure `$location` service with prefix `'!'`: +``` +myApp.config(function($locationProvider) { + $locationProvider.prefix('!'); +}); +``` + +If you enter the app at url `http:/myapp.com/#/myView` this error will be throw. + +The correct url for this configuration is `http:/myapp.com/#!/myView` (note the `'!'` after `'#'` symbol). diff --git a/docs/content/error/$location/ipthprfx.ngdoc b/docs/content/error/$location/ipthprfx.ngdoc new file mode 100644 index 00000000..55b75d86 --- /dev/null +++ b/docs/content/error/$location/ipthprfx.ngdoc @@ -0,0 +1,8 @@ +@ngdoc error +@name $location:ipthprfx +@fullName Invalid or Missing Path Prefix +@description + +This error occurs when you configure the {@link ng.$location `$location`} service in the html5 mode, specify a base url for your application via `` element and try to update the location with a path that doesn't match the base prefix. + +To resolve this issue, please check the base url specified via the `` tag in the head of your main html document, as well as the url that you tried to set the location to. diff --git a/docs/content/error/$location/isrcharg.ngdoc b/docs/content/error/$location/isrcharg.ngdoc new file mode 100644 index 00000000..4b60ddd5 --- /dev/null +++ b/docs/content/error/$location/isrcharg.ngdoc @@ -0,0 +1,9 @@ +@ngdoc error +@name $location:isrcharg +@fullName Wrong $location.search() argument type +@description + +To resolve this error, ensure that the first argument for the `$location.search` call is a `string` or an object. +You can use the stack trace associated with this error to identify the call site that caused this issue. + +To learn more, please consult the {@link ng.$location `$location`} api docs. 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: + +``` +
{{user.constructor.name}}
+``` 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. diff --git a/docs/content/error/$resource/badargs.ngdoc b/docs/content/error/$resource/badargs.ngdoc new file mode 100644 index 00000000..834c7826 --- /dev/null +++ b/docs/content/error/$resource/badargs.ngdoc @@ -0,0 +1,9 @@ +@ngdoc error +@name $resource:badargs +@fullName Too Many Arguments +@description + +This error occurs when specifying too many arguments to a {@link ngResource.$resource `$resource`} action, such as `get`, `query` or any user-defined custom action. +These actions may take up to 4 arguments. + +For more information, refer to the {@link ngResource.$resource `$resource`} API reference documentation. diff --git a/docs/content/error/$resource/badcfg.ngdoc b/docs/content/error/$resource/badcfg.ngdoc new file mode 100644 index 00000000..87e1ed26 --- /dev/null +++ b/docs/content/error/$resource/badcfg.ngdoc @@ -0,0 +1,11 @@ +@ngdoc error +@name $resource:badcfg +@fullName Response does not match configured parameter +@description + +This error occurs when the {@link ngResource.$resource `$resource`} service expects a response that can be deserialized as an array, receives an object, or vice versa. +By default, all resource actions expect objects, except `query` which expects arrays. + +To resolve this error, make sure your `$resource` configuration matches the actual format of the data returned from the server. + +For more information, see the {@link ngResource.$resource `$resource`} API reference documentation. diff --git a/docs/content/error/$resource/badmember.ngdoc b/docs/content/error/$resource/badmember.ngdoc new file mode 100644 index 00000000..4a61eb9b --- /dev/null +++ b/docs/content/error/$resource/badmember.ngdoc @@ -0,0 +1,27 @@ +@ngdoc error +@name $resource:badmember +@fullName Syntax error in param value using @member lookup +@description + +Occurs when there is a syntax error when attempting to extract a param +value from the data object. + +Here's an example of valid syntax for `params` or `paramsDefault`: + +````javascript +{ + bar: '@foo.bar' +} +```` + +The part following the `@`, `foo.bar` in this case, should be a simple +dotted member lookup using only ASCII identifiers. This error occurs +when there is an error in that expression. The following are all syntax +errors + + | Value | Error | + |---------|----------------| + | `@` | Empty expression following `@`. | + | `@1.a` | `1` is an invalid javascript identifier. | + | `@.a` | Leading `.` is invalid. | + | `@a[1]` | Only dotted lookups are supported (no index operator) | diff --git a/docs/content/error/$resource/badname.ngdoc b/docs/content/error/$resource/badname.ngdoc new file mode 100644 index 00000000..99f73bdc --- /dev/null +++ b/docs/content/error/$resource/badname.ngdoc @@ -0,0 +1,8 @@ +@ngdoc error +@name $resource:badname +@fullName Cannot use hasOwnProperty as a parameter name +@description + +Occurs when you try to use the name `hasOwnProperty` as a name of a parameter. +Generally, a name cannot be `hasOwnProperty` because it is used, internally, on a object +and allowing such a name would break lookups on this object. \ No newline at end of file diff --git a/docs/content/error/$rootScope/infdig.ngdoc b/docs/content/error/$rootScope/infdig.ngdoc new file mode 100644 index 00000000..e36f1d69 --- /dev/null +++ b/docs/content/error/$rootScope/infdig.ngdoc @@ -0,0 +1,17 @@ +@ngdoc error +@name $rootScope:infdig +@fullName Infinite $digest Loop +@description + +This error occurs when the application's model becomes unstable and each `$digest` cycle triggers a state change and subsequent `$digest` cycle. +Angular detects this situation and prevents an infinite loop from causing the browser to become unresponsive. + +For example, the situation can occur by setting up a watch on a path and subsequently updating the same path when the value changes. + +``` +$scope.$watch('foo', function() { + $scope.foo = $scope.foo + 1; +}); +``` + +The maximum number of allowed iterations of the `$digest` cycle is controlled via TTL setting which can be configured via {@link ng.$rootScopeProvider $rootScopeProvider}. diff --git a/docs/content/error/$rootScope/inprog.ngdoc b/docs/content/error/$rootScope/inprog.ngdoc new file mode 100644 index 00000000..375f8fe8 --- /dev/null +++ b/docs/content/error/$rootScope/inprog.ngdoc @@ -0,0 +1,74 @@ +@ngdoc error +@name $rootScope:inprog +@fullName Action Already In Progress +@description + +At any point in time there can be only one `$digest` or $apply operation in progress. +The stack trace of this error allows you to trace the origin of the currently executing $apply or $digest call. + +`$digest` or `$apply` are processing operational states of the Scope - data-structure in Angular that provides context for models and enables model mutation observation. + +Trying to reenter a `$digest` or `$apply` while one of them is already in progress is typically a sign of programming error that needs to be fixed. + +This error is often seen when interacting with an API that is sometimes sync and sometimes async. + +For example: + +``` +function MyController() { + thirdPartyComponent.getData(function(someData) { + scope.$apply(function() { + scope.someData = someData; + }); + }); +} +``` + +The controller constructor is always instantiated from within an $apply cycle, so if the third-party component called our callback synchronously, we'd be trying to enter the $apply again. + +To resolve this type of issue, either fix the api to be always synchronous or asynchronous or wrap the call to the api with setTimeout call to make it always asynchronous. + + +Other situation that leads to this error is when you are trying to reuse a function to by using it as a callback for code that is called by various apis inside and outside of $apply. + +For example: + +``` +myApp.directive('myDirective', function() { + return { + link: function($scope, $element) { + function doSomeWork() { + $scope.$apply(function() { + // do work here, and update the model + }; + } + + $element.on('click', doSomeWork); + doSomeWork(); // << this will throw an exception because templates are compiled within $apply + } + } +}); + +``` + +The fix for the example above looks like this: +``` +myApp.directive('myDirective', function() { + return { + link: function($scope, $element) { + function doSomeWork() { + // do work here, and update the model + } + + $element.on('click', function() { + $scope.$apply(doSomeWork); // <<< the $apply call was moved to the callsite that doesn't execute in $apply call already + }); + + doSomeWork(); + } + } +}); + +``` + +To learn more about Angular processing model please check out the {@link guide/concepts concepts doc} as well as the {@link ng.$rootScope.Scope api} doc. diff --git a/docs/content/error/$sanitize/badparse.ngdoc b/docs/content/error/$sanitize/badparse.ngdoc new file mode 100644 index 00000000..d07c6d62 --- /dev/null +++ b/docs/content/error/$sanitize/badparse.ngdoc @@ -0,0 +1,11 @@ +@ngdoc error +@name $sanitize:badparse +@fullName Parsing Error while Sanitizing +@description + +This error occurs when the HTML string passed to '$sanitize' can't be parsed by the sanitizer. +The error contains part of the html string that can't be parsed. + +The parser is more strict than a typical browser parser, so it's possible that some obscure input would produce this error despite the string being recognized as valid HTML by a browser. + +If a valid html code results in this error, please file a bug. diff --git a/docs/content/error/$sce/icontext.ngdoc b/docs/content/error/$sce/icontext.ngdoc new file mode 100644 index 00000000..e30b6ad4 --- /dev/null +++ b/docs/content/error/$sce/icontext.ngdoc @@ -0,0 +1,8 @@ +@ngdoc error +@name $sce:icontext +@fullName Invalid / Unknown SCE context +@description + +The context enum passed to {@link ng.$sce#methods_trustAs $sce.trustAs} was not recognized. + +Please consult the list of {@link ng.$sce#contexts supported Strict Contextual Escaping (SCE) contexts}. diff --git a/docs/content/error/$sce/iequirks.ngdoc b/docs/content/error/$sce/iequirks.ngdoc new file mode 100644 index 00000000..08afbf66 --- /dev/null +++ b/docs/content/error/$sce/iequirks.ngdoc @@ -0,0 +1,17 @@ +@ngdoc error +@name $sce:iequirks +@fullName IE8 in quirks mode is unsupported +@description + +This error occurs when you are using AngularJS with {@link ng.$sce Strict Contextual Escaping (SCE)} mode enabled (the default) on IE8 or lower in quirks mode. + +In this mode, IE8 allows one to execute arbitrary javascript by the use of the `expression()` syntax and is not supported. +Refer +[MSDN Blogs > IEBlog > Ending Expressions](http://blogs.msdn.com/b/ie/archive/2008/10/16/ending-expressions.aspx) +to learn more about them. + +To resolve this error please specify the proper doctype at the top of your main html document: + +``` + +``` diff --git a/docs/content/error/$sce/imatcher.ngdoc b/docs/content/error/$sce/imatcher.ngdoc new file mode 100644 index 00000000..eabdbc53 --- /dev/null +++ b/docs/content/error/$sce/imatcher.ngdoc @@ -0,0 +1,9 @@ +@ngdoc error +@name $sce:imatcher +@fullName Invalid matcher (only string patterns and RegExp instances are supported) +@description + +Please see {@link ng.$sceDelegateProvider#methods_resourceUrlWhitelist +$sceDelegateProvider.resourceUrlWhitelist} and {@link +api/ng.$sceDelegateProvider#methods_resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} for the +list of acceptable items. diff --git a/docs/content/error/$sce/insecurl.ngdoc b/docs/content/error/$sce/insecurl.ngdoc new file mode 100644 index 00000000..67bbb2b6 --- /dev/null +++ b/docs/content/error/$sce/insecurl.ngdoc @@ -0,0 +1,26 @@ +@ngdoc error +@name $sce:insecurl +@fullName Processing of a Resource from Untrusted Source Blocked +@description + +AngularJS' {@link ng.$sce Strict Contextual Escaping (SCE)} mode (enabled by default) has blocked loading a resource from an insecure URL. + +Typically, this would occur if you're attempting to load an Angular template from an untrusted source. +It's also possible that a custom directive threw this error for a similar reason. + +Angular only loads templates from trusted URLs (by calling {@link ng.$sce#methods_getTrustedResourceUrl $sce.getTrustedResourceUrl} on the template URL). + +By default, only URLs that belong to the same origin are trusted. These are urls with the same domain and protocol as the application document. + +The {@link ng.directive:ngInclude ngInclude} directive and {@link guide/directive directives} that specify a `templateUrl` require a trusted resource URL. + +To load templates from other domains and/or protocols, either adjust the {@link +api/ng.$sceDelegateProvider#methods_resourceUrlWhitelist whitelist}/ {@link +api/ng.$sceDelegateProvider#methods_resourceUrlBlacklist blacklist} or wrap the URL with a call to {@link +api/ng.$sce#methods_trustAsResourceUrl $sce.trustAsResourceUrl}. + +**Note**: The browser's [Same Origin +Policy](https://code.google.com/p/browsersec/wiki/Part2#Same-origin_policy_for_XMLHttpRequest) and +[Cross-Origin Resource Sharing (CORS)](http://www.w3.org/TR/cors/) policy apply +that may further restrict whether the template is successfully loaded. (e.g. neither cross-domain +requests won't work on all browsers nor `file://` requests on some browsers) diff --git a/docs/content/error/$sce/itype.ngdoc b/docs/content/error/$sce/itype.ngdoc new file mode 100644 index 00000000..cc2a6f62 --- /dev/null +++ b/docs/content/error/$sce/itype.ngdoc @@ -0,0 +1,8 @@ +@ngdoc error +@name $sce:itype +@fullName String Value is Required for SCE Trust Call +@description + +{@link ng.$sce#methods_trustAs $sce.trustAs} requires a string value. + +Read more about {@link ng.$sce Strict Contextual Escaping (SCE)} in AngularJS. diff --git a/docs/content/error/$sce/iwcard.ngdoc b/docs/content/error/$sce/iwcard.ngdoc new file mode 100644 index 00000000..83facf1d --- /dev/null +++ b/docs/content/error/$sce/iwcard.ngdoc @@ -0,0 +1,9 @@ +@ngdoc error +@name $sce:iwcard +@fullName The sequence *** is not a valid pattern wildcard +@description + +The strings in {@link ng.$sceDelegateProvider#methods_resourceUrlWhitelist +$sceDelegateProvider.resourceUrlWhitelist} and {@link +api/ng.$sceDelegateProvider#methods_resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} may not +contain the undefined sequence `***`. Only `*` and `**` wildcard patterns are defined. diff --git a/docs/content/error/$sce/unsafe.ngdoc b/docs/content/error/$sce/unsafe.ngdoc new file mode 100644 index 00000000..fdddf61b --- /dev/null +++ b/docs/content/error/$sce/unsafe.ngdoc @@ -0,0 +1,15 @@ +@ngdoc error +@name $sce:unsafe +@fullName Require a safe/trusted value +@description + +The value provided for use in a specific context was not found to be safe/trusted for use. + +Angular's {@link ng.$sce Strict Contextual Escaping (SCE)} mode +(enabled by default), requires bindings in certain +contexts to result in a value that is trusted as safe for use in such a context. (e.g. loading an +Angular template from a URL requires that the URL is one considered safe for loading resources.) + +This helps prevent XSS and other security issues. Read more at {@link +api/ng.$sce Strict Contextual Escaping (SCE)} + diff --git a/docs/content/error/animate/notcsel.ngdoc b/docs/content/error/animate/notcsel.ngdoc deleted file mode 100644 index d8ceaa0e..00000000 --- a/docs/content/error/animate/notcsel.ngdoc +++ /dev/null @@ -1,6 +0,0 @@ -@ngdoc error -@name $animate:notcsel -@fullName Not class CSS selector -@description - -Expecting a CSS selector for class. Class selectors must start with `.`, for example: `.my-class-name`. diff --git a/docs/content/error/cacheFactory/iid.ngdoc b/docs/content/error/cacheFactory/iid.ngdoc deleted file mode 100644 index 62e985e8..00000000 --- a/docs/content/error/cacheFactory/iid.ngdoc +++ /dev/null @@ -1,8 +0,0 @@ -@ngdoc error -@name $cacheFactory:iid -@fullName Invalid ID -@description - -This error occurs when trying to create a new `cache` object via {@link ng.$cacheFactory} with an ID that was already used to create another cache object. - -To resolve the error please use a different cache ID when calling `$cacheFactory`. diff --git a/docs/content/error/compile/ctreq.ngdoc b/docs/content/error/compile/ctreq.ngdoc deleted file mode 100644 index 47c876a3..00000000 --- a/docs/content/error/compile/ctreq.ngdoc +++ /dev/null @@ -1,49 +0,0 @@ -@ngdoc error -@name $compile:ctreq -@fullName Missing Required Controller -@description - -This error occurs when {@link ng.$compile HTML compiler} tries to process a directive that specifies the {@link ng.$compile#description_comprehensive-directive-api_directive-definition-object `require` option} in a {@link ng.$compile#description_comprehensive-directive-api directive definition}, -but the required directive controller is not present on the current DOM element (or its ancestor element, if `^` was specified). - -To resolve this error ensure that there is no typo in the required controller name and that the required directive controller is present on the current element. - -If the required controller is expected to be on a ancestor element, make ensure that you prefix the controller name in the `require` definition with `^`. - -If the required controller is optionally requested, use `?` or `^?` to specify that. - - -Example of a directive that requires {@link ng.directive:ngModel ngModel} controller: -``` -myApp.directive('myDirective', function() { - return { - require: 'ngModel', - ... - } -} -``` - -This directive can then be used as: -``` - -``` - - -Example of a directive that optionally requires a {@link ng.directive:form form} controller from an ancestor: -``` -myApp.directive('myDirective', function() { - return { - require: '^?form', - ... - } -} -``` - -This directive can then be used as: -``` -
-
- -
-
-``` diff --git a/docs/content/error/compile/iscp.ngdoc b/docs/content/error/compile/iscp.ngdoc deleted file mode 100644 index 1450dec9..00000000 --- a/docs/content/error/compile/iscp.ngdoc +++ /dev/null @@ -1,25 +0,0 @@ -@ngdoc error -@name $compile:iscp -@fullName Invalid Isolate Scope Definition -@description - -When declaring isolate scope the scope definition object must be in specific format which starts with mode character (`@&=`) with an optional local name. - -``` -myModule.directive('directiveName', function factory() { - return { - ... - scope: { - 'attrName': '@', // OK - 'attrName2': '=localName', // OK - 'attrName3': 'name', // ERROR: missing mode @&= - 'attrName4': ' = name', // ERROR: extra spaces - 'attrName5': 'name=', // ERROR: must be prefixed with @&= - } - ... - } -}); -``` - -Please refer to the {@link ng.$compile#description_comprehensive-directive-api_directive-definition-object -`scope` option} of the directive definition documentation to learn more about the API. diff --git a/docs/content/error/compile/multidir.ngdoc b/docs/content/error/compile/multidir.ngdoc deleted file mode 100644 index 439d82c7..00000000 --- a/docs/content/error/compile/multidir.ngdoc +++ /dev/null @@ -1,17 +0,0 @@ -@ngdoc error -@name $compile:multidir -@fullName Multiple Directive Resource Contention -@description - -This error occurs when multiple directives are applied to the same DOM element, and -processing them would result in a collision or an unsupported configuration. - - -To resolve this issue remove one of the directives which is causing the collision. - -Example scenarios of multiple incompatible directives applied to the same element include: - -* Multiple directives requesting `isolated scope`. -* Multiple directives publishing a controller under the same name. -* Multiple directives declared with the `transclusion` option. -* Multiple directives attempting to define a `template` or `templateURL`. diff --git a/docs/content/error/compile/nodomevents.ngdoc b/docs/content/error/compile/nodomevents.ngdoc deleted file mode 100644 index ed1888c7..00000000 --- a/docs/content/error/compile/nodomevents.ngdoc +++ /dev/null @@ -1,20 +0,0 @@ -@ngdoc error -@name $compile:nodomevents -@fullName Interpolated Event Attributes -@description - -This error occurs when one tries to create a binding for event handler attributes like `onclick`, `onload`, `onsubmit`, etc. - -There is no practical value in binding to these attributes and doing so only exposes your application to security vulnerabilities like XSS. -For these reasons binding to event handler attributes (all attributes that start with `on` and `formaction` attribute) is not supported. - - -An example code that would allow XSS vulnerability by evaluating user input in the window context could look like this: -``` - -
click me
-``` - -Since the `onclick` evaluates the value as JavaScript code in the window context, setting the `username` model to a value like `javascript:alert('PWND')` would result in script injection when the `div` is clicked. - - diff --git a/docs/content/error/compile/nonassign.ngdoc b/docs/content/error/compile/nonassign.ngdoc deleted file mode 100644 index 3a7d996b..00000000 --- a/docs/content/error/compile/nonassign.ngdoc +++ /dev/null @@ -1,41 +0,0 @@ -@ngdoc error -@name $compile:nonassign -@fullName Non-Assignable Expression -@description - -This error occurs when a directive defines an isolate scope property -(using the `=` mode in the {@link ng.$compile#description_comprehensive-directive-api_directive-definition-object -`scope` option} of a directive definition) but the directive is used with an expression that is not-assignable. - -In order for the two-way data-binding to work, it must be possible to write new values back into the path defined with the expression. - -For example, given a directive: - -``` -myModule.directive('myDirective', function factory() { - return { - ... - scope: { - 'bind': '=localValue' - } - ... - } -}); -``` - -Following are invalid uses of this directive: -``` - - - - - -``` - - -To resolve this error, always use path expressions with scope properties that are two-way data-bound: -``` - - -``` - diff --git a/docs/content/error/compile/selmulti.ngdoc b/docs/content/error/compile/selmulti.ngdoc deleted file mode 100644 index 51221ad8..00000000 --- a/docs/content/error/compile/selmulti.ngdoc +++ /dev/null @@ -1,20 +0,0 @@ -@ngdoc error -@name $compile:selmulti -@fullName Binding to Multiple Attribute -@description - -Binding to the `multiple` attribute of `select` element is not supported since switching between multiple and single mode changes the {@link ng.directive:ngModel `ngModel`} object type from instance to array of instances which breaks the model semantics. - -If you need to use different types of `select` elements in your template based on some variable, please use {@link ng.directive:ngIf ngIf} or {@link ng.directive:ngSwitch ngSwitch} directives to select one of them to be used at runtime. - - -Example with invalid usage: -``` - -``` - -Example that uses ngIf to pick one of the `select` elements based on a variable: -``` - - -``` diff --git a/docs/content/error/compile/tpload.ngdoc b/docs/content/error/compile/tpload.ngdoc deleted file mode 100644 index b2b4fb2d..00000000 --- a/docs/content/error/compile/tpload.ngdoc +++ /dev/null @@ -1,11 +0,0 @@ -@ngdoc error -@name $compile:tpload -@fullName Error Loading Template -@description - -This error occurs when {@link ng.$compile `$compile`} attempts to fetch a template from some URL, and the request fails. - -To resolve this error, ensure that the URL of the template is spelled correctly and resolves to correct absolute URL. -The [Chrome Developer Tools](https://developers.google.com/chrome-developer-tools/docs/network#network_panel_overview) might also be helpful in determining why the request failed. - -If you are using {@link ng.$templateCache} to pre-load templates, ensure that the cache was populated with the template. diff --git a/docs/content/error/compile/tplrt.ngdoc b/docs/content/error/compile/tplrt.ngdoc deleted file mode 100644 index 3c29dbdc..00000000 --- a/docs/content/error/compile/tplrt.ngdoc +++ /dev/null @@ -1,39 +0,0 @@ -@ngdoc error -@name $compile:tplrt -@fullName Invalid Template Root -@description - -When a directive is declared with `template` (or `templateUrl`) and `replace` mode on, the template -must have exactly one root element. That is, the text of the template property or the content -referenced by the templateUrl must be contained within a single html element. -For example, `

blah blah blah

` instead of simply `blah blah blah`. -Otherwise, the replacement operation would result in a single element (the directive) being replaced -with multiple elements or nodes, which is unsupported and not commonly needed in practice. - - -For example a directive with definition: - -``` -myModule.directive('myDirective', function factory() { - return { - ... - replace: true, - templateUrl: 'someUrl' - ... - } -}); -``` - -And a template provided at URL `someUrl`. The template must be an html fragment that has only a -single root element, like the `div` element in this template: - -``` -
Hello World!
-``` - -An an invalid template to be used with this directive is one that defines multiple root nodes or -elements. For example: - -``` -Hello World! -``` diff --git a/docs/content/error/compile/uterdir.ngdoc b/docs/content/error/compile/uterdir.ngdoc deleted file mode 100644 index c1f263f9..00000000 --- a/docs/content/error/compile/uterdir.ngdoc +++ /dev/null @@ -1,34 +0,0 @@ -@ngdoc error -@name $compile:uterdir -@fullName Unterminated Directive -@description - -This error occurs when using multi-element directives and a `directive-start` attribute fails to form a matching pair with a corresponding `directive-end` attribute. -A `directive-start` should have a matching `directive-end` on a sibling node in the DOM. For instance, - -``` - - I get repeated - I also get repeated -
-``` - -is a valid example. - -This error can occur in several different ways. One is by leaving out the `directive-end` attribute, like so: - -``` -
- -
-``` - -Another is by nesting a `directive-end` inside of `directive-start`, or vice versa: - -``` -
- -
-``` - -To avoid this error, make sure each `directive-start` you use has a matching `directive-end` on a sibling node in the DOM. diff --git a/docs/content/error/controller/noscp.ngdoc b/docs/content/error/controller/noscp.ngdoc deleted file mode 100644 index 26257546..00000000 --- a/docs/content/error/controller/noscp.ngdoc +++ /dev/null @@ -1,21 +0,0 @@ -@ngdoc error -@name $controller:noscp -@fullName Missing $scope object -@description - -This error occurs when {@link ng.$controller $controller} service is called in order to instantiate a new controller but no scope is provided via `$scope` property of the locals map. - -Example of incorrect usage that leads to this error: -``` -$controller(MyController); -//or -$controller(MyController, {scope: newScope}); -``` - -To fix the example above please provide a scope to the $controller call: - -``` -$controller(MyController, {$scope, newScope}); -``` - -Please consult the {@link ng.$controller $controller} service api docs to learn more. diff --git a/docs/content/error/httpBackend/noxhr.ngdoc b/docs/content/error/httpBackend/noxhr.ngdoc deleted file mode 100644 index e2d5901d..00000000 --- a/docs/content/error/httpBackend/noxhr.ngdoc +++ /dev/null @@ -1,10 +0,0 @@ -@ngdoc error -@name $httpBackend:noxhr -@fullName Unsupported XHR -@description - -This error occurs in browsers that do not support XmlHttpRequest. AngularJS -supports Safari, Chrome, Firefox, Opera, IE8 and higher, and mobile browsers -(Android, Chrome Mobile, iOS Safari). To avoid this error, use an officially -supported browser. - diff --git a/docs/content/error/injector/cdep.ngdoc b/docs/content/error/injector/cdep.ngdoc deleted file mode 100644 index 0e6526b8..00000000 --- a/docs/content/error/injector/cdep.ngdoc +++ /dev/null @@ -1,26 +0,0 @@ -@ngdoc error -@name $injector:cdep -@fullName Circular Dependency -@description - -This error occurs when the {@link angular.injector $injector} tries to get -a service that depends on itself, either directly or indirectly. To fix this, -construct your dependency chain such that there are no circular dependencies. - -For example: - -``` -angular.module('myApp', []) - .factory('myService', function (myService) { - // ... - }) - .controller('MyCtrl', function ($scope, myService) { - // ... - }); -``` - -When an instance of `MyCtrl` is created, the service `myService` will be created -by the `$injector`. `myService` depends on itself, which causes the `$injector` -to detect a circular dependency and throw the error. - -For more information, see the {@link guide/di Dependency Injection Guide}. \ No newline at end of file diff --git a/docs/content/error/injector/itkn.ngdoc b/docs/content/error/injector/itkn.ngdoc deleted file mode 100644 index 5437dce7..00000000 --- a/docs/content/error/injector/itkn.ngdoc +++ /dev/null @@ -1,26 +0,0 @@ -@ngdoc error -@name $injector:itkn -@fullName Bad Injection Token -@description - -This error occurs when using a bad token as a dependency injection annotation. -Dependency injection annotation tokens should always be strings. Using any other -type will cause this error to be thrown. - -Examples of code with bad injection tokens include: - -``` -var myCtrl = function ($scope, $http) { /* ... */ }; -myCtrl.$inject = ['$scope', 42]; - -myAppModule.controller('MyCtrl', ['$scope', {}, function ($scope, $timeout) { - // ... -}]); -``` - -The bad injection tokens are `42` in the first example and `{}` in the second. -To avoid the error, always use string literals for dependency injection annotation -tokens. - -For an explanation of what injection annotations are and how to use them, refer -to the {@link guide/di Dependency Injection Guide}. \ No newline at end of file diff --git a/docs/content/error/injector/modulerr.ngdoc b/docs/content/error/injector/modulerr.ngdoc deleted file mode 100644 index 4b92a5de..00000000 --- a/docs/content/error/injector/modulerr.ngdoc +++ /dev/null @@ -1,11 +0,0 @@ -@ngdoc error -@name $injector:modulerr -@fullName Module Error -@description - -This error occurs when a module fails to load due to some exception. The error -message above should provide additional context. - -In AngularJS `1.2.0` and later, `ngRoute` has been moved to its own module. -If you are getting this error after upgrading to `1.2.x`, be sure that you've -installed {@link ngRoute `ngRoute`}. diff --git a/docs/content/error/injector/nomod.ngdoc b/docs/content/error/injector/nomod.ngdoc deleted file mode 100644 index 5f8fb1e6..00000000 --- a/docs/content/error/injector/nomod.ngdoc +++ /dev/null @@ -1,26 +0,0 @@ -@ngdoc error -@name $injector:nomod -@fullName Module Unavailable -@description - -This error occurs when trying to "re-open" a module that has not yet been defined. - -To define a new module, call {@link angular.module angular.module} with a name -and an array of dependent modules, like so: - -``` -// When defining a module with no module dependencies, -// the requires array should be defined and empty. -var myApp = angular.module('myApp', []); -``` - -To retrieve a reference to the same module for further configuration, call -`angular.module` without the `requires` array. - -``` -var myApp = angular.module('myApp'); -``` - -Calling `angular.module` without the `requires` array when the module has not yet -been defined causes this error to be thrown. To fix it, define your module with -a name and an empty array, as in the first example above. \ No newline at end of file diff --git a/docs/content/error/injector/pget.ngdoc b/docs/content/error/injector/pget.ngdoc deleted file mode 100644 index 1772d348..00000000 --- a/docs/content/error/injector/pget.ngdoc +++ /dev/null @@ -1,26 +0,0 @@ -@ngdoc error -@name $injector:pget -@fullName Provider Missing $get -@description - -This error occurs when attempting to register a provider that does not have a -`$get` method. For example: - -``` -function BadProvider() {} // No $get method! -angular.module("myApp", []) - .provider('bad', BadProvider); // this throws the error -``` - -To fix the error, fill in the `$get` method on the provider like so: - -``` -function GoodProvider() { - this.$get = angular.noop; -} -angular.module("myApp", []) - .provider('good', GoodProvider); -``` - -For more information, refer to the {@link auto.$provide#methods_provider -$provide.provider} api doc. \ No newline at end of file diff --git a/docs/content/error/injector/unpr.ngdoc b/docs/content/error/injector/unpr.ngdoc deleted file mode 100644 index 1b0faa8e..00000000 --- a/docs/content/error/injector/unpr.ngdoc +++ /dev/null @@ -1,26 +0,0 @@ -@ngdoc error -@name $injector:unpr -@fullName Unknown Provider -@description - -This error results from the `$injector` being unable to resolve a required -dependency. To fix this, make sure the dependency is defined and spelled -correctly. For example: - -``` -angular.module('myApp', []) - .controller('myCtrl', ['myService', function (myService) { - // Do something with myService - }]); -``` - -This code will fail with `$injector:unpr` if `myService` is not defined. Making -sure each dependency is defined will fix the problem. - -``` -angular.module('myApp', []) - .service('myService', function () { /* ... */ }) - .controller('myCtrl', ['myService', function (myService) { - // Do something with myService - }]); -``` \ No newline at end of file diff --git a/docs/content/error/interpolate/interr.ngdoc b/docs/content/error/interpolate/interr.ngdoc deleted file mode 100644 index 8d56c8d0..00000000 --- a/docs/content/error/interpolate/interr.ngdoc +++ /dev/null @@ -1,7 +0,0 @@ -@ngdoc error -@name $interpolate:interr -@fullName Interpolation Error -@description - -This error occurs when interpolation fails due to some exception. The error -message above should provide additional context. diff --git a/docs/content/error/interpolate/noconcat.ngdoc b/docs/content/error/interpolate/noconcat.ngdoc deleted file mode 100644 index 0853544e..00000000 --- a/docs/content/error/interpolate/noconcat.ngdoc +++ /dev/null @@ -1,12 +0,0 @@ -@ngdoc error -@name $interpolate:noconcat -@fullName Multiple Expressions -@description - -This error occurs when performing an interpolation that concatenates multiple -expressions when a trusted value is required. Concatenating expressions makes -it hard to reason about whether some combination of concatenated values are -unsafe to use and could easily lead to XSS. - -For more information about how AngularJS helps keep your app secure, refer to -the {@link ng.$sce $sce} API doc. \ No newline at end of file diff --git a/docs/content/error/location/ihshprfx.ngdoc b/docs/content/error/location/ihshprfx.ngdoc deleted file mode 100644 index 8acab933..00000000 --- a/docs/content/error/location/ihshprfx.ngdoc +++ /dev/null @@ -1,17 +0,0 @@ -@ngdoc error -@name $location:ihshprfx -@fullName Missing Hash Prefix -@description - -This error occurs when {@link ng.$location $location} service is configured to use a hash prefix but this prefix was not present in a url that the `$location` service was asked to parse. - -For example if you configure `$location` service with prefix `'!'`: -``` -myApp.config(function($locationProvider) { - $locationProvider.prefix('!'); -}); -``` - -If you enter the app at url `http:/myapp.com/#/myView` this error will be throw. - -The correct url for this configuration is `http:/myapp.com/#!/myView` (note the `'!'` after `'#'` symbol). diff --git a/docs/content/error/location/ipthprfx.ngdoc b/docs/content/error/location/ipthprfx.ngdoc deleted file mode 100644 index 55b75d86..00000000 --- a/docs/content/error/location/ipthprfx.ngdoc +++ /dev/null @@ -1,8 +0,0 @@ -@ngdoc error -@name $location:ipthprfx -@fullName Invalid or Missing Path Prefix -@description - -This error occurs when you configure the {@link ng.$location `$location`} service in the html5 mode, specify a base url for your application via `` element and try to update the location with a path that doesn't match the base prefix. - -To resolve this issue, please check the base url specified via the `` tag in the head of your main html document, as well as the url that you tried to set the location to. diff --git a/docs/content/error/location/isrcharg.ngdoc b/docs/content/error/location/isrcharg.ngdoc deleted file mode 100644 index 4b60ddd5..00000000 --- a/docs/content/error/location/isrcharg.ngdoc +++ /dev/null @@ -1,9 +0,0 @@ -@ngdoc error -@name $location:isrcharg -@fullName Wrong $location.search() argument type -@description - -To resolve this error, ensure that the first argument for the `$location.search` call is a `string` or an object. -You can use the stack trace associated with this error to identify the call site that caused this issue. - -To learn more, please consult the {@link ng.$location `$location`} api docs. 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: - -``` -
{{user.constructor.name}}
-``` 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. diff --git a/docs/content/error/resource/badargs.ngdoc b/docs/content/error/resource/badargs.ngdoc deleted file mode 100644 index 834c7826..00000000 --- a/docs/content/error/resource/badargs.ngdoc +++ /dev/null @@ -1,9 +0,0 @@ -@ngdoc error -@name $resource:badargs -@fullName Too Many Arguments -@description - -This error occurs when specifying too many arguments to a {@link ngResource.$resource `$resource`} action, such as `get`, `query` or any user-defined custom action. -These actions may take up to 4 arguments. - -For more information, refer to the {@link ngResource.$resource `$resource`} API reference documentation. diff --git a/docs/content/error/resource/badcfg.ngdoc b/docs/content/error/resource/badcfg.ngdoc deleted file mode 100644 index 87e1ed26..00000000 --- a/docs/content/error/resource/badcfg.ngdoc +++ /dev/null @@ -1,11 +0,0 @@ -@ngdoc error -@name $resource:badcfg -@fullName Response does not match configured parameter -@description - -This error occurs when the {@link ngResource.$resource `$resource`} service expects a response that can be deserialized as an array, receives an object, or vice versa. -By default, all resource actions expect objects, except `query` which expects arrays. - -To resolve this error, make sure your `$resource` configuration matches the actual format of the data returned from the server. - -For more information, see the {@link ngResource.$resource `$resource`} API reference documentation. diff --git a/docs/content/error/resource/badmember.ngdoc b/docs/content/error/resource/badmember.ngdoc deleted file mode 100644 index 4a61eb9b..00000000 --- a/docs/content/error/resource/badmember.ngdoc +++ /dev/null @@ -1,27 +0,0 @@ -@ngdoc error -@name $resource:badmember -@fullName Syntax error in param value using @member lookup -@description - -Occurs when there is a syntax error when attempting to extract a param -value from the data object. - -Here's an example of valid syntax for `params` or `paramsDefault`: - -````javascript -{ - bar: '@foo.bar' -} -```` - -The part following the `@`, `foo.bar` in this case, should be a simple -dotted member lookup using only ASCII identifiers. This error occurs -when there is an error in that expression. The following are all syntax -errors - - | Value | Error | - |---------|----------------| - | `@` | Empty expression following `@`. | - | `@1.a` | `1` is an invalid javascript identifier. | - | `@.a` | Leading `.` is invalid. | - | `@a[1]` | Only dotted lookups are supported (no index operator) | diff --git a/docs/content/error/resource/badname.ngdoc b/docs/content/error/resource/badname.ngdoc deleted file mode 100644 index 99f73bdc..00000000 --- a/docs/content/error/resource/badname.ngdoc +++ /dev/null @@ -1,8 +0,0 @@ -@ngdoc error -@name $resource:badname -@fullName Cannot use hasOwnProperty as a parameter name -@description - -Occurs when you try to use the name `hasOwnProperty` as a name of a parameter. -Generally, a name cannot be `hasOwnProperty` because it is used, internally, on a object -and allowing such a name would break lookups on this object. \ No newline at end of file diff --git a/docs/content/error/rootScope/infdig.ngdoc b/docs/content/error/rootScope/infdig.ngdoc deleted file mode 100644 index e36f1d69..00000000 --- a/docs/content/error/rootScope/infdig.ngdoc +++ /dev/null @@ -1,17 +0,0 @@ -@ngdoc error -@name $rootScope:infdig -@fullName Infinite $digest Loop -@description - -This error occurs when the application's model becomes unstable and each `$digest` cycle triggers a state change and subsequent `$digest` cycle. -Angular detects this situation and prevents an infinite loop from causing the browser to become unresponsive. - -For example, the situation can occur by setting up a watch on a path and subsequently updating the same path when the value changes. - -``` -$scope.$watch('foo', function() { - $scope.foo = $scope.foo + 1; -}); -``` - -The maximum number of allowed iterations of the `$digest` cycle is controlled via TTL setting which can be configured via {@link ng.$rootScopeProvider $rootScopeProvider}. diff --git a/docs/content/error/rootScope/inprog.ngdoc b/docs/content/error/rootScope/inprog.ngdoc deleted file mode 100644 index 375f8fe8..00000000 --- a/docs/content/error/rootScope/inprog.ngdoc +++ /dev/null @@ -1,74 +0,0 @@ -@ngdoc error -@name $rootScope:inprog -@fullName Action Already In Progress -@description - -At any point in time there can be only one `$digest` or $apply operation in progress. -The stack trace of this error allows you to trace the origin of the currently executing $apply or $digest call. - -`$digest` or `$apply` are processing operational states of the Scope - data-structure in Angular that provides context for models and enables model mutation observation. - -Trying to reenter a `$digest` or `$apply` while one of them is already in progress is typically a sign of programming error that needs to be fixed. - -This error is often seen when interacting with an API that is sometimes sync and sometimes async. - -For example: - -``` -function MyController() { - thirdPartyComponent.getData(function(someData) { - scope.$apply(function() { - scope.someData = someData; - }); - }); -} -``` - -The controller constructor is always instantiated from within an $apply cycle, so if the third-party component called our callback synchronously, we'd be trying to enter the $apply again. - -To resolve this type of issue, either fix the api to be always synchronous or asynchronous or wrap the call to the api with setTimeout call to make it always asynchronous. - - -Other situation that leads to this error is when you are trying to reuse a function to by using it as a callback for code that is called by various apis inside and outside of $apply. - -For example: - -``` -myApp.directive('myDirective', function() { - return { - link: function($scope, $element) { - function doSomeWork() { - $scope.$apply(function() { - // do work here, and update the model - }; - } - - $element.on('click', doSomeWork); - doSomeWork(); // << this will throw an exception because templates are compiled within $apply - } - } -}); - -``` - -The fix for the example above looks like this: -``` -myApp.directive('myDirective', function() { - return { - link: function($scope, $element) { - function doSomeWork() { - // do work here, and update the model - } - - $element.on('click', function() { - $scope.$apply(doSomeWork); // <<< the $apply call was moved to the callsite that doesn't execute in $apply call already - }); - - doSomeWork(); - } - } -}); - -``` - -To learn more about Angular processing model please check out the {@link guide/concepts concepts doc} as well as the {@link ng.$rootScope.Scope api} doc. diff --git a/docs/content/error/sanitize/badparse.ngdoc b/docs/content/error/sanitize/badparse.ngdoc deleted file mode 100644 index d07c6d62..00000000 --- a/docs/content/error/sanitize/badparse.ngdoc +++ /dev/null @@ -1,11 +0,0 @@ -@ngdoc error -@name $sanitize:badparse -@fullName Parsing Error while Sanitizing -@description - -This error occurs when the HTML string passed to '$sanitize' can't be parsed by the sanitizer. -The error contains part of the html string that can't be parsed. - -The parser is more strict than a typical browser parser, so it's possible that some obscure input would produce this error despite the string being recognized as valid HTML by a browser. - -If a valid html code results in this error, please file a bug. diff --git a/docs/content/error/sce/icontext.ngdoc b/docs/content/error/sce/icontext.ngdoc deleted file mode 100644 index e30b6ad4..00000000 --- a/docs/content/error/sce/icontext.ngdoc +++ /dev/null @@ -1,8 +0,0 @@ -@ngdoc error -@name $sce:icontext -@fullName Invalid / Unknown SCE context -@description - -The context enum passed to {@link ng.$sce#methods_trustAs $sce.trustAs} was not recognized. - -Please consult the list of {@link ng.$sce#contexts supported Strict Contextual Escaping (SCE) contexts}. diff --git a/docs/content/error/sce/iequirks.ngdoc b/docs/content/error/sce/iequirks.ngdoc deleted file mode 100644 index 08afbf66..00000000 --- a/docs/content/error/sce/iequirks.ngdoc +++ /dev/null @@ -1,17 +0,0 @@ -@ngdoc error -@name $sce:iequirks -@fullName IE8 in quirks mode is unsupported -@description - -This error occurs when you are using AngularJS with {@link ng.$sce Strict Contextual Escaping (SCE)} mode enabled (the default) on IE8 or lower in quirks mode. - -In this mode, IE8 allows one to execute arbitrary javascript by the use of the `expression()` syntax and is not supported. -Refer -[MSDN Blogs > IEBlog > Ending Expressions](http://blogs.msdn.com/b/ie/archive/2008/10/16/ending-expressions.aspx) -to learn more about them. - -To resolve this error please specify the proper doctype at the top of your main html document: - -``` - -``` diff --git a/docs/content/error/sce/imatcher.ngdoc b/docs/content/error/sce/imatcher.ngdoc deleted file mode 100644 index eabdbc53..00000000 --- a/docs/content/error/sce/imatcher.ngdoc +++ /dev/null @@ -1,9 +0,0 @@ -@ngdoc error -@name $sce:imatcher -@fullName Invalid matcher (only string patterns and RegExp instances are supported) -@description - -Please see {@link ng.$sceDelegateProvider#methods_resourceUrlWhitelist -$sceDelegateProvider.resourceUrlWhitelist} and {@link -api/ng.$sceDelegateProvider#methods_resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} for the -list of acceptable items. diff --git a/docs/content/error/sce/insecurl.ngdoc b/docs/content/error/sce/insecurl.ngdoc deleted file mode 100644 index 67bbb2b6..00000000 --- a/docs/content/error/sce/insecurl.ngdoc +++ /dev/null @@ -1,26 +0,0 @@ -@ngdoc error -@name $sce:insecurl -@fullName Processing of a Resource from Untrusted Source Blocked -@description - -AngularJS' {@link ng.$sce Strict Contextual Escaping (SCE)} mode (enabled by default) has blocked loading a resource from an insecure URL. - -Typically, this would occur if you're attempting to load an Angular template from an untrusted source. -It's also possible that a custom directive threw this error for a similar reason. - -Angular only loads templates from trusted URLs (by calling {@link ng.$sce#methods_getTrustedResourceUrl $sce.getTrustedResourceUrl} on the template URL). - -By default, only URLs that belong to the same origin are trusted. These are urls with the same domain and protocol as the application document. - -The {@link ng.directive:ngInclude ngInclude} directive and {@link guide/directive directives} that specify a `templateUrl` require a trusted resource URL. - -To load templates from other domains and/or protocols, either adjust the {@link -api/ng.$sceDelegateProvider#methods_resourceUrlWhitelist whitelist}/ {@link -api/ng.$sceDelegateProvider#methods_resourceUrlBlacklist blacklist} or wrap the URL with a call to {@link -api/ng.$sce#methods_trustAsResourceUrl $sce.trustAsResourceUrl}. - -**Note**: The browser's [Same Origin -Policy](https://code.google.com/p/browsersec/wiki/Part2#Same-origin_policy_for_XMLHttpRequest) and -[Cross-Origin Resource Sharing (CORS)](http://www.w3.org/TR/cors/) policy apply -that may further restrict whether the template is successfully loaded. (e.g. neither cross-domain -requests won't work on all browsers nor `file://` requests on some browsers) diff --git a/docs/content/error/sce/itype.ngdoc b/docs/content/error/sce/itype.ngdoc deleted file mode 100644 index cc2a6f62..00000000 --- a/docs/content/error/sce/itype.ngdoc +++ /dev/null @@ -1,8 +0,0 @@ -@ngdoc error -@name $sce:itype -@fullName String Value is Required for SCE Trust Call -@description - -{@link ng.$sce#methods_trustAs $sce.trustAs} requires a string value. - -Read more about {@link ng.$sce Strict Contextual Escaping (SCE)} in AngularJS. diff --git a/docs/content/error/sce/iwcard.ngdoc b/docs/content/error/sce/iwcard.ngdoc deleted file mode 100644 index 83facf1d..00000000 --- a/docs/content/error/sce/iwcard.ngdoc +++ /dev/null @@ -1,9 +0,0 @@ -@ngdoc error -@name $sce:iwcard -@fullName The sequence *** is not a valid pattern wildcard -@description - -The strings in {@link ng.$sceDelegateProvider#methods_resourceUrlWhitelist -$sceDelegateProvider.resourceUrlWhitelist} and {@link -api/ng.$sceDelegateProvider#methods_resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} may not -contain the undefined sequence `***`. Only `*` and `**` wildcard patterns are defined. diff --git a/docs/content/error/sce/unsafe.ngdoc b/docs/content/error/sce/unsafe.ngdoc deleted file mode 100644 index fdddf61b..00000000 --- a/docs/content/error/sce/unsafe.ngdoc +++ /dev/null @@ -1,15 +0,0 @@ -@ngdoc error -@name $sce:unsafe -@fullName Require a safe/trusted value -@description - -The value provided for use in a specific context was not found to be safe/trusted for use. - -Angular's {@link ng.$sce Strict Contextual Escaping (SCE)} mode -(enabled by default), requires bindings in certain -contexts to result in a value that is trusted as safe for use in such a context. (e.g. loading an -Angular template from a URL requires that the URL is one considered safe for loading resources.) - -This helps prevent XSS and other security issues. Read more at {@link -api/ng.$sce Strict Contextual Escaping (SCE)} - -- cgit v1.2.3