Skip to content

Commit 1443805

Browse files
vojtajinaIgorMinar
vojtajina
authored and
IgorMinar
committed
docs: correct broken links
This also contains some whitespace corrections by my editor.
1 parent e8cc85f commit 1443805

39 files changed

Lines changed: 209 additions & 208 deletions

‎docs/content/cookbook/mvc.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,4 +125,4 @@ board variable.
125125
* The view can call any controller function.
126126
* In this example, the `setUrl()` and `readUrl()` functions copy the game state to/from the URL's
127127
hash so the browser's back button will undo game steps. See deep-linking. This example calls {@link
128-
api/ng.$rootScope.Scope#$watch $watch()} to set up a listener that invokes `readUrl()` when needed.
128+
api/ng.$rootScope.Scope#methods_$watch $watch()} to set up a listener that invokes `readUrl()` when needed.

‎docs/content/error/compile/ctreq.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
@fullName Missing Required Controller
44
@description
55

6-
This error occurs when {@link api/ng.$compile template compiler} tries process the directive that specifies the `require` option in a {@link guide/directive#directivedefinitionobject directive definition},
6+
This error occurs when {@link api/ng.$compile template compiler} tries process the directive that specifies the `require` option in a {@link guide/directive#writing-directives_directive-definition-object directive definition},
77
but the required directive controller is not present on the current DOM element (or its ancestor element, if `^` was specified).
88

99
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.

‎docs/content/error/compile/iscp.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,4 +21,4 @@ myModule.directive('directiveName', function factory() {
2121
});
2222
```
2323

24-
Please refer to the {@link guide/directive#directivedefinitionobject directive definition docs} to learn more about the api.
24+
Please refer to the {@link guide/directive#writing-directives_directive-definition-object directive definition docs} to learn more about the api.

‎docs/content/error/compile/nonassign.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
@fullName Non-Assignable Expression
44
@description
55

6-
This error occurs when a directive defines an isolate scope property that support two-way data-binding (using the `=` mode in the {@link guide/directive#directivedefinitionobject directive definition}) but the directive is used with an expression that is not-assignable.
6+
This error occurs when a directive defines an isolate scope property that support two-way data-binding (using the `=` mode in the {@link guide/directive#writing-directives_directive-definition-object directive definition}) but the directive is used with an expression that is not-assignable.
77

88
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.
99

‎docs/content/error/injector/pget.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,5 +22,5 @@ angular.module("myApp", [])
2222
.provider('good', GoodProvider);
2323
```
2424

25-
For more information, refer to the {@link api/AUTO.$provide#provider
25+
For more information, refer to the {@link api/AUTO.$provide#methods_provider
2626
$provide.provider} api doc.

‎docs/content/error/jqLite/nosel.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
@fullName Unsupported Selector Lookup
44
@description
55

6-
In order to keep Angular small, Angular implements only a subset of the selectors in {@link api/angular.element#angularsjqlite jqLite}.
6+
In order to keep Angular small, Angular implements only a subset of the selectors in {@link api/angular.element#description_angulars-jqlite jqLite}.
77
This error occurs when a jqLite instance is invoked with a selector other than this subset.
88

99
In order to resolve this error, rewrite your code to only use tag name selectors and manually traverse the DOM using the APIs provided by jqLite.

‎docs/content/error/sce/icontext.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,6 @@
33
@fullName Invalid / Unknown SCE context
44
@description
55

6-
The context enum passed to {@link api/ng.$sce#trustAs $sce.trustAs} was not recognized.
6+
The context enum passed to {@link api/ng.$sce#methods_trustAs $sce.trustAs} was not recognized.
77

88
Please consult the list of {@link api/ng.$sce#contexts supported Strict Contextual Escaping (SCE) contexts}.

‎docs/content/error/sce/iequirks.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
@fullName IE8 in quirks mode is unsupported
44
@description
55

6-
This error occurs when you are using AngularJS with {@link api/ng.$sce#strictcontextualescaping Strict Contextual Escaping (SCE)} mode enabled (the default) on IE8 or lower in quirks mode.
6+
This error occurs when you are using AngularJS with {@link api/ng.$sce Strict Contextual Escaping (SCE)} mode enabled (the default) on IE8 or lower in quirks mode.
77

88
In this mode, IE8 allows one to execute arbitrary javascript by the use of the `expression()` syntax and is not supported.
99
Refer {@link http://blogs.msdn.com/b/ie/archive/2008/10/16/ending-expressions.aspx MSDN Blogs > IEBlog > Ending Expressions} to learn more about them.

‎docs/content/error/sce/imatcher.ngdoc‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
@fullName Invalid matcher (only string patterns and RegExp instances are supported)
44
@description
55

6-
Please see {@link api/ng.$sceDelegateProvider#resourceUrlWhitelist
6+
Please see {@link api/ng.$sceDelegateProvider#methods_resourceUrlWhitelist
77
$sceDelegateProvider.resourceUrlWhitelist} and {@link
8-
api/ng.$sceDelegateProvider#resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} for the
8+
api/ng.$sceDelegateProvider#methods_resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} for the
99
list of acceptable items.

‎docs/content/error/sce/insecurl.ngdoc‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,21 +3,21 @@
33
@fullName Processing of a Resource from Untrusted Source Blocked
44
@description
55

6-
AngularJS' {@link api/ng.$sce#strictcontextualescaping Strict Contextual Escaping (SCE)} mode (enabled by default) has blocked loading a resource from an insecure URL.
6+
AngularJS' {@link api/ng.$sce Strict Contextual Escaping (SCE)} mode (enabled by default) has blocked loading a resource from an insecure URL.
77

88
Typically, this would occur if you're attempting to load an Angular template from an untrusted source.
99
It's also possible that a custom directive threw this error for a similar reason.
1010

11-
Angular only loads templates from trusted URLs (by calling {@link api/ng.$sce#getTrustedResourceUrl $sce.getTrustedResourceUrl} on the template URL).
11+
Angular only loads templates from trusted URLs (by calling {@link api/ng.$sce#methods_getTrustedResourceUrl $sce.getTrustedResourceUrl} on the template URL).
1212

1313
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.
1414

1515
The {@link api/ng.directive:ngInclude ngInclude} directive and {@link guide/directive directives} that specify a `templateUrl` require a trusted resource URL.
1616

1717
To load templates from other domains and/or protocols, either adjust the {@link
18-
api/ng.$sceDelegateProvider#resourceUrlWhitelist whitelist}/ {@link
19-
api/ng.$sceDelegateProvider#resourceUrlBlacklist blacklist} or wrap the URL with a call to {@link
20-
api/ng.$sce#trustAsResourceUrl $sce.trustAsResourceUrl}.
18+
api/ng.$sceDelegateProvider#methods_resourceUrlWhitelist whitelist}/ {@link
19+
api/ng.$sceDelegateProvider#methods_resourceUrlBlacklist blacklist} or wrap the URL with a call to {@link
20+
api/ng.$sce#methods_trustAsResourceUrl $sce.trustAsResourceUrl}.
2121

2222
**Note**: The browser's {@link
2323
https://code.google.com/p/browsersec/wiki/Part2#Same-origin_policy_for_XMLHttpRequest Same Origin

0 commit comments

Comments
 (0)