tiennm99/styleguide
1
0
Fork 0
mirror of https://github.com/tiennm99/styleguide.git synced 2026-09-03 18:17:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Replaced HTTP where HTTPS been awailable.

Browse Source
This commit is contained in:
Ackermann Yuriy
2016-04-01 21:41:34 +13:00
parent acb4f9016f
commit 7969290bac
19 changed files with 155 additions and 155 deletions
Download Patch File Download Diff File Expand all files Collapse all files
javascriptguide.xml
+10 -10
View File
@@ -355,7 +355,7 @@
first appear! </p>
<p>For that reason, it is best to use <code>goog.inherits()</code> from
<a href="http://code.google.com/closure/library/">
<a href="https://code.google.com/closure/library/">
the Closure Library
</a>
or a similar library function.
@@ -804,7 +804,7 @@
<p>Many JavaScript libraries, including
<a href="http://code.google.com/closure/library/">
<a href="https://code.google.com/closure/library/">
the Closure Library
</a>
and
@@ -1135,7 +1135,7 @@
<a href="https://docs.google.com/document/pub?id=1ETFAuh2kaXMVL-vafUYhaWlhl6b5D9TOvboVg7Zl68Y"><code>goog.scope</code></a>
may be used to shorten references to
namespaced symbols in programs using
<a href="http://code.google.com/closure/library/">the Closure
<a href="https://code.google.com/closure/library/">the Closure
Library</a>.</p>
<p>Only one <code>goog.scope</code> invocation may be added per
file. Always place it in the global scope.</p>
@@ -1301,7 +1301,7 @@
functions, and properties.</p>
<p>The --jscomp_warning=visibility compiler flag turns on compiler
warnings for visibility violations. See
<a href="http://code.google.com/p/closure-compiler/wiki/Warnings">
<a href="https://code.google.com/p/closure-compiler/wiki/Warnings">
Closure Compiler
Warnings</a>.
</p>
@@ -2220,7 +2220,7 @@
</p>
<p>All files, classes, methods and properties should be documented with
<a href="http://code.google.com/p/jsdoc-toolkit/">JSDoc</a>
<a href="https://code.google.com/p/jsdoc-toolkit/">JSDoc</a>
comments with the appropriate <a href="#JSDoc_Tag_Reference">tags</a>
and <a href="#JsTypes">types</a>. Textual descriptions for properties,
methods, method parameters and method return values should be included
@@ -2235,7 +2235,7 @@
<SUBSECTION title="Comment Syntax">
<p>The JSDoc syntax is based on
<a href="http://www.oracle.com/technetwork/java/javase/documentation/index-137868.html">
<a href="https://www.oracle.com/technetwork/java/javase/documentation/index-137868.html">
JavaDoc</a>. Many tools extract metadata from JSDoc comments to
perform code validation and optimizations. These comments must be
well-formed.</p>
@@ -2322,7 +2322,7 @@
*/
</CODE_SNIPPET>
The <a href="http://www.oracle.com/technetwork/java/javase/documentation/index-137868.html">
The <a href="https://www.oracle.com/technetwork/java/javase/documentation/index-137868.html">
JavaDoc</a> style guide is a useful resource on how to write
well-formed doc comments.
</SUBSECTION>
@@ -2860,7 +2860,7 @@
For example, <code>@type {Foo}</code> means "an instance of Foo",
but <code>@lends {Foo}</code> means "the constructor Foo".<p/>
The <a href="http://code.google.com/p/jsdoc-toolkit/wiki/TagLends">
The <a href="https://code.google.com/p/jsdoc-toolkit/wiki/TagLends">
JSDoc Toolkit docs</a> have more information on this
annotation.
</td>
@@ -3313,7 +3313,7 @@
<p>
You may also see other types of JSDoc annotations in third-party
code. These annotations appear in the
<a href="http://code.google.com/p/jsdoc-toolkit/wiki/TagReference">
<a href="https://code.google.com/p/jsdoc-toolkit/wiki/TagReference">
JSDoc Toolkit Tag Reference
</a>
but are currently discouraged in Google code. You should consider
@@ -3389,7 +3389,7 @@
<p>Use of JS compilers such as the
<a href="http://code.google.com/closure/compiler/">Closure Compiler</a>
<a href="https://code.google.com/closure/compiler/">Closure Compiler</a>
is required for all customer-facing code.</p>