Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

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

+209
-208
lines changed

‎docs/content/cookbook/mvc.ngdoc

+1-1
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

+1-1
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

+1-1
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

+1-1
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

+1-1
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

+1-1
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

+1-1
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

+1-1
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

+2-2
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

+5-5
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

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

+2-2
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,6 @@
33
@fullName String Value is Required for SCE Trust Call
44
@description
55

6-
{@link api/ng.$sce#trustAs $sce.trustAs} requires a string value.
6+
{@link api/ng.$sce#methods_trustAs $sce.trustAs} requires a string value.
77

8-
Read more about {@link api/ng.$sce#strictcontextualescaping Strict Contextual Escaping (SCE)} in AngularJS.
8+
Read more about {@link api/ng.$sce Strict Contextual Escaping (SCE)} in AngularJS.

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

+2-2
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
@fullName The sequence *** is not a valid pattern wildcard
44
@description
55

6-
The strings in {@link api/ng.$sceDelegateProvider#resourceUrlWhitelist
6+
The strings in {@link api/ng.$sceDelegateProvider#methods_resourceUrlWhitelist
77
$sceDelegateProvider.resourceUrlWhitelist} and {@link
8-
api/ng.$sceDelegateProvider#resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} may not
8+
api/ng.$sceDelegateProvider#methods_resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} may not
99
contain the undefined sequence `***`. Only `*` and `**` wildcard patterns are defined.

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

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@
55

66
The value provided for use in a specific context was not found to be safe/trusted for use.
77

8-
Angular's {@link api/ng.$sce#strictcontextualescaping Strict Contextual Escaping (SCE)} mode
8+
Angular's {@link api/ng.$sce Strict Contextual Escaping (SCE)} mode
99
(enabled by default), requires bindings in certain
1010
contexts to result in a value that is trusted as safe for use in such a context. (e.g. loading an
1111
Angular template from a URL requires that the URL is one considered safe for loading resources.)
1212

1313
This helps prevent XSS and other security issues. Read more at {@link
14-
api/ng.$sce#strictcontextualescaping Strict Contextual Escaping (SCE)}
14+
api/ng.$sce Strict Contextual Escaping (SCE)}
1515

‎docs/content/guide/animations.ngdoc

+7-7
Original file line numberDiff line numberDiff line change
@@ -253,13 +253,13 @@ The table below explains in detail which animation events are triggered
253253

254254
| Directive | Supported Animations |
255255
|-------------------------------------------------------------------------------------|------------------------------------------|
256-
| {@link api/ng.directive:ngRepeat#animations ngRepeat} | enter, leave, and move |
257-
| {@link api/ngRoute.directive:ngView#animations ngView} | enter and leave |
258-
| {@link api/ng.directive:ngInclude#animations ngInclude} | enter and leave |
259-
| {@link api/ng.directive:ngSwitch#animations ngSwitch} | enter and leave |
260-
| {@link api/ng.directive:ngIf#animations ngIf} | enter and leave |
261-
| {@link api/ng.directive:ngShow#animations ngClass or {{class}}} | add and remove |
262-
| {@link api/ng.directive:ngShow#animations ngShow & ngHide} | add and remove (the ng-hide class value) |
256+
| {@link api/ng.directive:ngRepeat#usage_animations ngRepeat} | enter, leave, and move |
257+
| {@link api/ngRoute.directive:ngView#usage_animations ngView} | enter and leave |
258+
| {@link api/ng.directive:ngInclude#usage_animations ngInclude} | enter and leave |
259+
| {@link api/ng.directive:ngSwitch#usage_animations ngSwitch} | enter and leave |
260+
| {@link api/ng.directive:ngIf#usage_animations ngIf} | enter and leave |
261+
| {@link api/ng.directive:ngShow#usage_animations ngClass or {{class}}} | add and remove |
262+
| {@link api/ng.directive:ngShow#usage_animations ngShow & ngHide} | add and remove (the ng-hide class value) |
263263

264264
For a full breakdown of the steps involved during each animation event, refer to the {@link api/ngAnimate.$animate API docs}.
265265

‎docs/content/guide/compiler.ngdoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
Angular's {@link api/ng.$compile HTML compiler} allows the developer to teach the
88
browser new HTML syntax. The compiler allows you to attach behavior to any HTML element or attribute
99
and even create new HTML elements or attributes with custom behavior. Angular calls these behavior
10-
extensions {@link api/ng.$compileProvider#directive directives}.
10+
extensions {@link api/ng.$compileProvider#methods_directive directives}.
1111

1212
HTML has a lot of constructs for formatting the HTML for static documents in a declarative fashion.
1313
For example if something needs to be centered, there is no need to provide instructions to the
@@ -59,7 +59,7 @@ api/ng.directive:ngBind `ng-bind`} directive.
5959
</pre>
6060

6161
A directive is just a function which executes when the compiler encounters it in the DOM. See {@link
62-
api/ng.$compileProvider#directive directive API} for in-depth documentation on how
62+
api/ng.$compileProvider#methods_directive directive API} for in-depth documentation on how
6363
to write directives.
6464

6565
Here is a directive which makes any element draggable. Notice the `draggable` attribute on the

‎docs/content/guide/concepts.ngdoc

+18-18
Original file line numberDiff line numberDiff line change
@@ -75,26 +75,26 @@ directive which is handling the event. An explicit call to $apply is needed only
7575
implementing custom event callbacks, or when working with third-party library callbacks.
7676

7777
1. Enter Angular execution context by calling {@link guide/scope scope}`.`{@link
78-
api/ng.$rootScope.Scope#$apply $apply}`(stimulusFn)`. Where `stimulusFn` is
78+
api/ng.$rootScope.Scope#methods_$apply $apply}`(stimulusFn)`. Where `stimulusFn` is
7979
the work you wish to do in Angular execution context.
8080
2. Angular executes the `stimulusFn()`, which typically modifies application state.
81-
3. Angular enters the {@link api/ng.$rootScope.Scope#$digest $digest} loop. The
81+
3. Angular enters the {@link api/ng.$rootScope.Scope#methods_$digest $digest} loop. The
8282
loop is made up of two smaller loops which process {@link
83-
api/ng.$rootScope.Scope#$evalAsync $evalAsync} queue and the {@link
84-
api/ng.$rootScope.Scope#$watch $watch} list. The {@link
85-
api/ng.$rootScope.Scope#$digest $digest} loop keeps iterating until the model
86-
stabilizes, which means that the {@link api/ng.$rootScope.Scope#$evalAsync
87-
$evalAsync} queue is empty and the {@link api/ng.$rootScope.Scope#$watch
83+
api/ng.$rootScope.Scope#methods_$evalAsync $evalAsync} queue and the {@link
84+
api/ng.$rootScope.Scope#methods_$watch $watch} list. The {@link
85+
api/ng.$rootScope.Scope#methods_$digest $digest} loop keeps iterating until the model
86+
stabilizes, which means that the {@link api/ng.$rootScope.Scope#methods_$evalAsync
87+
$evalAsync} queue is empty and the {@link api/ng.$rootScope.Scope#methods_$watch
8888
$watch} list does not detect any changes.
89-
4. The {@link api/ng.$rootScope.Scope#$evalAsync $evalAsync} queue is used to
89+
4. The {@link api/ng.$rootScope.Scope#methods_$evalAsync $evalAsync} queue is used to
9090
schedule work which needs to occur outside of current stack frame, but before the browser's
9191
view render. This is usually done with `setTimeout(0)`, but the `setTimeout(0)` approach
9292
suffers from slowness and may cause view flickering since the browser renders the view after
9393
each event.
94-
5. The {@link api/ng.$rootScope.Scope#$watch $watch} list is a set of expressions
94+
5. The {@link api/ng.$rootScope.Scope#methods_$watch $watch} list is a set of expressions
9595
which may have changed since last iteration. If a change is detected then the `$watch`
9696
function is called which typically updates the DOM with the new value.
97-
6. Once the Angular {@link api/ng.$rootScope.Scope#$digest $digest} loop finishes
97+
6. Once the Angular {@link api/ng.$rootScope.Scope#methods_$digest $digest} loop finishes
9898
the execution leaves the Angular and JavaScript context. This is followed by the browser
9999
re-rendering the DOM to reflect any changes.
100100

@@ -107,17 +107,17 @@ user enters text into the text field.
107107
api/ng.directive:input input} {@link guide/directive
108108
directive} set up a `keydown` listener on the `<input>` control.
109109
2. the {@link api/ng.$interpolate &#123;&#123;name&#125;&#125; } interpolation
110-
sets up a {@link api/ng.$rootScope.Scope#$watch $watch} to be notified of
110+
sets up a {@link api/ng.$rootScope.Scope#methods_$watch $watch} to be notified of
111111
`name` changes.
112112
2. During the runtime phase:
113113
1. Pressing an '`X`' key causes the browser to emit a `keydown` event on the input control.
114114
2. The {@link api/ng.directive:input input} directive
115115
captures the change to the input's value and calls {@link
116-
api/ng.$rootScope.Scope#$apply $apply}`("name = 'X';")` to update the
116+
api/ng.$rootScope.Scope#methods_$apply $apply}`("name = 'X';")` to update the
117117
application model inside the Angular execution context.
118118
3. Angular applies the `name = 'X';` to the model.
119-
4. The {@link api/ng.$rootScope.Scope#$digest $digest} loop begins
120-
5. The {@link api/ng.$rootScope.Scope#$watch $watch} list detects a change
119+
4. The {@link api/ng.$rootScope.Scope#methods_$digest $digest} loop begins
120+
5. The {@link api/ng.$rootScope.Scope#methods_$watch $watch} list detects a change
121121
on the `name` property and notifies the {@link api/ng.$interpolate
122122
&#123;&#123;name&#125;&#125; } interpolation, which in turn updates the DOM.
123123
6. Angular exits the execution context, which in turn exits the `keydown` event and with it
@@ -253,7 +253,7 @@ rendering the view compared to most other templating systems.
253253
template sprinkled in.) The browser parses the HTML into the DOM, and the DOM becomes the input to
254254
the template engine known as the {@link api/ng.$compile compiler}. The compiler
255255
looks for {@link guide/directive directives} which in turn set up {@link
256-
api/ng.$rootScope.Scope#$watch watches} on the model. The result is a
256+
api/ng.$rootScope.Scope#methods_$watch watches} on the model. The result is a
257257
continuously updating view which does not need template model re-merging. Your model becomes
258258
the single source-of-truth for your view.
259259

@@ -377,8 +377,8 @@ as a {@link api/AUTO.$provide provider}.
377377

378378

379379
But the real magic of the {@link api/AUTO.$injector injector} is that it can be
380-
used to {@link api/AUTO.$injector#invoke call} methods and {@link
381-
api/AUTO.$injector#instantiate instantiate} types. This subtle feature is what
380+
used to {@link api/AUTO.$injector#methods_invoke call} methods and {@link
381+
api/AUTO.$injector#methods_instantiate instantiate} types. This subtle feature is what
382382
allows the methods and types to ask for their dependencies instead of having to look for them.
383383

384384
<pre>
@@ -406,7 +406,7 @@ allows the methods and types to ask for their dependencies instead of having to
406406

407407
Notice that the only thing you needed to write was the function, and list the dependencies in the
408408
function arguments. When angular calls the function, it will use the {@link
409-
api/AUTO.$injector#invoke call} which will automatically fill the function
409+
api/AUTO.$injector#methods_invoke call} which will automatically fill the function
410410
arguments.
411411

412412
Examine the `ClockCtrl` below, and notice how it lists the dependencies in the constructor. When the

0 commit comments

Comments
 (0)