8000 point to the current URL for documenting Closure Compiler tags and ty… · seanpm2001/jsdoc.github.io@723546c · GitHub
[go: up one dir, main page]
Skip to content

Commit 723546c

Browse files
hegemonichegemonic
committed
point to the current URL for documenting Closure Compiler tags and type expressions (jsdoc#155)
1 parent 9057468 commit 723546c

10 files changed

+13
-13
lines changed

‎about-configuring-jsdoc.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ <h2 id="configuration-file">Configuration File</h2>
7070
<p>This means:</p>
7171
<ul>
7272
<li>JSDoc allows you to use unrecognized tags (<code>tags.allowUnknownTags</code>);</li>
73-
<li>Both standard JSDoc tags and <a href="https://developers.google.com/closure/compiler/docs/js-for-compiler#tags">Closure Compiler tags</a> are enabled (
73+
<li>Both standard JSDoc tags and <a href="https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#jsdoc-tags">Closure Compiler tags</a> are enabled (
7474
<code>tags.dictionaries</code>);</li>
7575
<li>Only files ending in &quot;.js&quot;, &quot;.jsdoc&quot;, and &quot;.jsx&quot; will be processed (<code>source.includePattern</code>);</li>
7676
<li>Any file starting with an underscore or in a directory starting with an underscore will be
@@ -225,7 +225,7 @@ <h2 id="tags-and-tag-dictionaries">Tags and tag dictionaries</h2>
225225
</p>
226226
<ul>
227227
<li><code>jsdoc</code>: Core JSDoc tags.</li>
228-
<li><code>closure</code>: <a href="https://developers.google.com/closure/compiler/docs/js-for-compiler#tags">Closure Compiler tags</a>.</li>
228+
<li><code>closure</code>: <a href="https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#jsdoc-tags">Closure Compiler tags</a>.</li>
229229
</ul>
230230
<p>By default, both dictionaries are enabled. Also, by default, the <code>jsdoc</code> dictionary is listed first; as a result, if the <code>jsdoc</code> dictionary
231231
handles a tag differently than the <code>closure</code> dictionary, the

‎content/en/about-configuring-jsdoc.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ These options and others will be further explained on this page.
5252
Further settings may be added to the file as requested by various plugins or templates (for example,
5353
the [Markdown plugin][markdown] can be configured by including a "markdown" key).
5454

55-
[closure-tags]: https://developers.google.com/closure/compiler/docs/js-for-compiler#tags
55+
[closure-tags]: https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#jsdoc-tags
5656
[markdown]: plugins-markdown.html
5757

5858

@@ -288,4 +288,4 @@ can also change this setting to `["closure","jsdoc"]` if you want to allow core
288288
want to ensure that Closure Compiler-specific tags are interpreted as Closure Compiler would
289289
interpret them.
290290

291-
[closure-tags]: https://developers.google.com/closure/compiler/docs/js-for-compiler#tags
291+
[closure-tags]: https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#jsdoc-tags

‎content/en/tags-interface.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ With the [Closure Compiler][closure] tag dictionary:
1616

1717
`@interface`
1818

19-
[closure]: https://developers.google.com/closure/compiler/docs/js-for-compiler#tags
19+
[closure]: https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#jsdoc-tags
2020

2121

2222
## Overview

‎content/en/tags-private.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ With the [Closure Compiler][closure] tag dictionary:
2020

2121
`@private [{typeExpression}]`
2222

23-
[closure]: https://developers.google.com/closure/compiler/docs/js-for-compiler#tags
23+
[closure]: https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#jsdoc-tags
2424

2525

2626
## Overview

‎content/en/tags-protected.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ With the [Closure Compiler][closure] tag dictionary:
2020

2121
`@protected [{typeExpression}]`
2222

23-
[closure]: https://developers.google.com/closure/compiler/docs/js-for-compiler#tags
23+
[closure]: https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#jsdoc-tags
2424

2525

2626
## Overview

‎content/en/tags-type.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -263,7 +263,7 @@ var props;
263263
</tr>
264264
</table>
265265

266-
[closure]: https://developers.google.com/closure/compiler/docs/js-for-compiler#types
266+
[closure]: https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#type-expressions
267267
[param-tag]: tags-param.html
268268

269269

‎tags-interface.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ <h2 id="syntax">Syntax</h2>
4141
<p>With the JSDoc tag dictionary (enabled by default):</p>
4242
<p><code>@interface [&lt;name&gt;]</code>
4343
</p>
44-
<p>With the <a href="https://developers.google.com/closure/compiler/docs/js-for-compiler#tags">Closure Compiler</a> tag dictionary:</p>
44+
<p>With the <a href="https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#jsdoc-tags">Closure Compiler</a> tag dictionary:</p>
4545
<p><code>@interface</code>
4646
</p>
4747
<h2 id="overview">Overview</h2>

‎tags-private.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ <h2 id="syntax">Syntax</h2>
4141
<p>With the JSDoc tag dictionary (enabled by default):</p>
4242
<p><code>@private</code>
4343
</p>
44-
<p>With the <a href="https://developers.google.com/closure/compiler/docs/js-for-compiler#tags">Closure Compiler</a> tag dictionary:</p>
44+
<p>With the <a href="https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#jsdoc-tags">Closure Compiler</a> tag dictionary:</p>
4545
<p><code>@private [{typeExpression}]</code>
4646
</p>
4747
<h2 id="overview">Overview</h2>

‎tags-protected.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ <h2 id="syntax">Syntax</h2>
4141
<p>With the JSDoc tag dictionary (enabled by default):</p>
4242
<p><code>@protected</code>
4343
</p>
44-
<p>With the <a href="https://developers.google.com/closure/compiler/docs/js-for-compiler#tags">Closure Compiler</a> tag dictionary:</p>
44+
<p>With the <a href="https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#jsdoc-tags">Closure Compiler</a> tag dictionary:</p>
4545
<p><code>@protected [{typeExpression}]</code>
4646
</p>
4747
<h2 id="overview">Overview</h2>

‎tags-type.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,8 +45,8 @@ <h2 id="overview">Overview</h2>
4545
can also include type expressions with many other JSDoc tags, such as the <a href="tags-param.html">@param tag</a>.</p>
4646
<p>A type expression can include the JSDoc namepath to a symbol (for example, <code>myNamespace.MyClass</code>); a built-in JavaScript type (for example, <code>string</code>);
4747
or a combination of these. You can use any
48-
<a href="https://developers.google.com/closure/compiler/docs/js-for-compiler#types">Google Closure Compiler type expression</a>, as well as several other formats
49-
that are specific to JSDoc.</p>
48+
<a href="https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#type-expressions">Google Closure Compiler type expression</a>,
49+
as well as several other formats that are specific to JSDoc.</p>
5050
<p>If JSDoc determines that a type expression is invalid, it will display an error and stop running. You can turn this error into a warning by running JSDoc with
5151
the <code>--lenient</code> option.</p>
5252
<p><strong>Note</strong>: Full support for Google Closure Compiler-style type expressions is available in JSDoc 3.2 and later. Earlier versions of JSDoc included

0 commit comments

Comments
 (0)
0