JSH318901: Remove debugger statements
JSH318902: Do not use bitwise operators
JSH318903: Use correct comparison
JSH318904: Use camelCase in variables
JSH318905: Use curly braces around blocks
JSH318906: Use correct === and !==
JSH318907: Use correct null comparisons
JSH318908: Do not use eval
JSH318909: Do not use a single expression
JSH318910: Use filter in for in loops
JSH318911: Use parens for immediate function invocations
JSH318912: Use correct indent
JSH318913: Define variable before it is used
JSH318914: Use correct line breakings
JSH318915: Use correct line breakings around commas
JSH318916: Do not make functions within a loop
JSH318917: Avoid multi line strings
JSH318918: Do not use empty blocks
JSH318920: Do not use 'new' for side effects
JSH318921: Use consistent of quotation marks
JSH318922: Do not use single case switch
JSH318923: Use regular expressions correctly
JSH318924: Avoid . in regexp literals
JSH318925: Declare variable before it is used
JSH318926: Avoid JavaScript URLs
JSH318927: Remove unused variables
JSH318928: Avoid redeclaring a variable
JSH318929: Avoid correct construction of objects and function
JSH318930: Avoid this in non-constructor functions
JSH318931: Do not use arguments.caller and arguments.callee
JSH318941: Use semicolon correctly
JSH318942: Define uppercase constructors
JSH318943: Do not use unary increment and decrement operators
JSH318944: Use semicolon in last statement
JSH318945: Use dot notation instead of []
JSH318946: Avoid trailing whitespaces
JSH318961: Do not exceed max number of formal parameters per function
JSH318962: Do not exceed max number of nested blocks in a function
JSH318963: Do not exceed max number of statements per function
JSH318964: Do not exceed max allowed cyclomatic complexity
JSH318965: Do not exceed max length of a line in code

JSH318941: Use semicolon correctly

This option suppresses warnings about missing semicolons. There is a lot of FUD about semicolon spread by quite a few people in the community. The common myths are that semicolons are required all the time (they are not) and that they are unreliable. JavaScript has rules about semicolons which are followed by all browsers so it is up to you to decide whether you should or should not use semicolons in your code. (JSHint option 'asi')

TypeName: UseSemicolonCorrectly
CheckId: JSH318941
Severity: Warning
Type: JavaScriptFile
Links

comments powered by Disqus

Copyright © 2013 RENCORE AB. All Rights Reserved

Disclaimer: The views and opinions expressed in this documentation and in SPCAF are those of the creators and do not necessarily reflect the opinions and recommendations of Microsoft or any member of Microsoft. All trademarks, service marks, collective marks, copyrights, registered names, and marks used or cited by this documentation are the property of their respective owners.

SharePoint Code Analysis Framework, Version 4.5.2.7855, see www.spcaf.com for more information