Remove trailing whitespaces in JavaScript Style Guide

This commit is contained in:
Michael Zhou committed 2016-03-28 15:05:44 -04:00
1 parent 8c09ccf840
commit 3c3c96b2c3
1 file changed
+40 -40
+40 -40
View File
@@ -2,10 +2,10 @@
<?xml-stylesheet type="text/xsl" href="styleguide.xsl"?> <?xml-stylesheet type="text/xsl" href="styleguide.xsl"?>
<GUIDE title="Google JavaScript Style Guide"> <GUIDE title="Google JavaScript Style Guide">
<p class="revision"> <p class="revision">
Revision 2.93 Revision 2.93
</p> </p>
<address> <address>
Aaron Whyte<br/> Aaron Whyte<br/>
Bob Jervis<br/> Bob Jervis<br/>
@@ -35,23 +35,23 @@
<CATEGORY title="Background"> <CATEGORY title="Background">
<p> <p>
JavaScript is the main client-side scripting language used JavaScript is the main client-side scripting language used
by many of Google's open-source by many of Google's open-source
projects. projects.
This style guide is a list of <em>do</em>s and <em>don't</em>s for This style guide is a list of <em>do</em>s and <em>don't</em>s for
JavaScript programs. JavaScript programs.
</p> </p>
</CATEGORY> </CATEGORY>
</OVERVIEW> </OVERVIEW>
<CATEGORY title="JavaScript Language Rules"> <CATEGORY title="JavaScript Language Rules">
<STYLEPOINT title="var"> <STYLEPOINT title="var">
<SUMMARY> <SUMMARY>
@@ -100,7 +100,7 @@
considered immutable only if they do not demonstrate observable considered immutable only if they do not demonstrate observable
state change. This is not enforced by the compiler.</p> state change. This is not enforced by the compiler.</p>
</SUBSECTION> </SUBSECTION>
<SUBSECTION title="Constant pointers (variables and properties)"> <SUBSECTION title="Constant pointers (variables and properties)">
@@ -759,7 +759,7 @@
<p>Optional and variable arguments can also be specified in <p>Optional and variable arguments can also be specified in
<code>@param</code> annotations. Although either convention is <code>@param</code> annotations. Although either convention is
acceptable to the compiler, using both together is preferred.</p> acceptable to the compiler, using both together is preferred.</p>
</SUBSECTION> </SUBSECTION>
<SUBSECTION title="Getters and Setters"> <SUBSECTION title="Getters and Setters">
@@ -801,8 +801,8 @@
... ...
}; };
</CODE_SNIPPET> </CODE_SNIPPET>
<p>Many JavaScript libraries, including <p>Many JavaScript libraries, including
<a href="http://code.google.com/closure/library/"> <a href="http://code.google.com/closure/library/">
the Closure Library the Closure Library
@@ -826,7 +826,7 @@
parent namespace know what you are doing. If you start a project parent namespace know what you are doing. If you start a project
that creates hats for sloths, make sure that the Sloth team knows that creates hats for sloths, make sure that the Sloth team knows
that you're using <code>sloth.hats</code>.</p> that you're using <code>sloth.hats</code>.</p>
</SUBSUBSECTION> </SUBSUBSECTION>
<SUBSUBSECTION title="Use different namespaces for external code and internal code"> <SUBSUBSECTION title="Use different namespaces for external code and internal code">
<p>"External code" is code that comes from outside your codebase, <p>"External code" is code that comes from outside your codebase,
@@ -867,8 +867,8 @@
goog.exportSymbol('foo.hats.BowlerHat', googleyhats.BowlerHat); goog.exportSymbol('foo.hats.BowlerHat', googleyhats.BowlerHat);
</CODE_SNIPPET> </CODE_SNIPPET>
</SUBSUBSECTION> </SUBSUBSECTION>
<SUBSUBSECTION title="Alias long type names to improve readability"> <SUBSUBSECTION title="Alias long type names to improve readability">
<p>Use local aliases for fully-qualified types if doing so improves <p>Use local aliases for fully-qualified types if doing so improves
@@ -937,7 +937,7 @@
and should contain no punctuation except for <code>-</code> or and should contain no punctuation except for <code>-</code> or
<code>_</code> (prefer <code>-</code> to <code>_</code>).</p> <code>_</code> (prefer <code>-</code> to <code>_</code>).</p>
</SUBSECTION> </SUBSECTION>
</BODY> </BODY>
</STYLEPOINT> </STYLEPOINT>
@@ -1807,9 +1807,9 @@
<tr> <tr>
<td> <td>
null null
</td> </td>
<td> <td>
<CODE_SNIPPET> <CODE_SNIPPET>
@@ -1821,9 +1821,9 @@
<tr> <tr>
<td> <td>
undefined undefined
</td> </td>
<td> <td>
<CODE_SNIPPET> <CODE_SNIPPET>
@@ -2099,7 +2099,7 @@
<code>MyClass</code> is initialized with a null value, it will issue <code>MyClass</code> is initialized with a null value, it will issue
a warning.</p> a warning.</p>
<p>Optional parameters to functions may be undefined at runtime, so if <p>Optional parameters to functions may be undefined at runtime, so if
they are assigned to class properties, those properties must be they are assigned to class properties, those properties must be
@@ -2329,7 +2329,7 @@
<SUBSECTION title="Top/File-Level Comments"> <SUBSECTION title="Top/File-Level Comments">
<p> <p>
A <a href="copyright.html">copyright notice</a> and author information are optional. A <a href="copyright.html">copyright notice</a> and author information are optional.
File overviews are generally recommended whenever a file consists of File overviews are generally recommended whenever a file consists of
more than a single class definition. The top level comment is more than a single class definition. The top level comment is
@@ -2346,7 +2346,7 @@
*/ */
</CODE_SNIPPET> </CODE_SNIPPET>
</SUBSECTION> </SUBSECTION>
<SUBSECTION title="Class Comments"> <SUBSECTION title="Class Comments">
@@ -2416,7 +2416,7 @@
<tr> <tr>
<td> <td>
<a name="tag-author">@author</a> <a name="tag-author">@author</a>
</td> </td>
<td> <td>
<code>@author username@google.com (first last)</code> <code>@author username@google.com (first last)</code>
@@ -2431,11 +2431,11 @@
<td> <td>
Document the author of a file or the owner of a test, Document the author of a file or the owner of a test,
generally only used in the <code>@fileoverview</code> comment. generally only used in the <code>@fileoverview</code> comment.
</td> </td>
</tr> </tr>
<tr> <tr>
<td><a name="tag-code">@code</a></td> <td><a name="tag-code">@code</a></td>
@@ -2728,11 +2728,11 @@
<td> <td>
<p> <p>
Declares an Declares an
externs file. externs file.
</p> </p>
</td> </td>
</tr> </tr>
@@ -2891,9 +2891,9 @@
</td> </td>
</tr> </tr>
<tr> <tr>
<td><a name="tag-noalias">@noalias</a></td> <td><a name="tag-noalias">@noalias</a></td>
@@ -3204,7 +3204,7 @@
<td> <td>
Suppresses warnings from tools. Warning categories are Suppresses warnings from tools. Warning categories are
separated by <code>|</code> or <code>,</code>. separated by <code>|</code> or <code>,</code>.
</td> </td>
</tr> </tr>
@@ -3303,12 +3303,12 @@
</td> </td>
</tr> </tr>
</tbody> </tbody>
</table> </table>
<p> <p>
You may also see other types of JSDoc annotations in third-party You may also see other types of JSDoc annotations in third-party
@@ -3386,15 +3386,15 @@
<STYLEPOINT title="Compiling"> <STYLEPOINT title="Compiling">
<SUMMARY>Required</SUMMARY> <SUMMARY>Required</SUMMARY>
<BODY> <BODY>
<p>Use of JS compilers such as the <p>Use of JS compilers such as the
<a href="http://code.google.com/closure/compiler/">Closure Compiler</a> <a href="http://code.google.com/closure/compiler/">Closure Compiler</a>
is required for all customer-facing code.</p> is required for all customer-facing code.</p>
</BODY> </BODY>
</STYLEPOINT> </STYLEPOINT>
@@ -3584,7 +3584,7 @@
</STYLEPOINT> </STYLEPOINT>
</CATEGORY> </CATEGORY>
<PARTING_WORDS> <PARTING_WORDS>
<p> <p>
@@ -3615,7 +3615,7 @@
Revision 2.93 Revision 2.93
</p> </p>
<address> <address>
Aaron Whyte<br/> Aaron Whyte<br/>
Bob Jervis<br/> Bob Jervis<br/>