edit-article

Article Description: {"UPDATE":"FEA #] # - JS select3 - code ","DESC":"linted"}

Chapter ID/Name:

Status: Write Writing Written

Add Photo:

Owner ID:

Content: use HTML Edit Content <h1 style="text-align: center;"><strong>rev-013</strong></h1> <h2><strong>UPDATE FEATURE #]&nbsp;# - code optimization JS select3_s.js&nbsp;</strong></h2> <ol> <li><strong>x] FILES = 1</strong></li> <ol> <li>x] JS select3_s - validate code using ls</li> </ol> <li><strong>*] WHAT=&nbsp;x] UPDATE FEATURE - &nbsp;JS select3_s.js - </strong>run this code through the 'js lint' tool for validating the js,&nbsp;</li> <ol> <li>*] this should be a best practice</li> <li>*] and also be part of an automated build process ( see how to article - where Visual Studio 'save' event triggers &nbsp;)</li> <li>BUT - time consuming b/c its very, very nitpicky about a lot of details that impact the readability and consistency of the code, BUT NOT the actual functionality of the script</li> <ol> <li>] spaces,&nbsp;</li> <li>] indentation - every brackets in exactly the right place,&nbsp;</li> <li>] format - every statement function name(arg1, arg2) {</li> <li>*] you can configure the tool with options to ignore certain things (ex messy whitespace) but &nbsp;if you start to ignore/tolerate a lot of what &nbsp;its checking why bother with checking in first place ???</li> </ol></ol> <li><strong>x] REPLACES=</strong></li> <ol> <li>x] none - updates existing page with perfectly formatted js code</li> </ol> <li><strong>x] DATE=</strong></li> <ol> <li>x] 2013-08-10</li> </ol></ol>