edit-article

Article Description: ] a listing of some javascript style guides, use these guides to develop consistent practices

Chapter ID/Name:

Status: Write Writing Written

Add Photo:

Owner ID:

Content: use HTML Edit Content <h1 style="text-align: center;">style guide</h1> <h2>[WHAT]</h2> <ol> <li>]&nbsp;a style guide is a collection of ?practices<span style="text-decoration: line-through;">patterns</span>? for writing software source code, the theory is that by having multiple developers adhere to a consistent style of writing code, the code will be easier to maintain in the future, and easier to work with in the now,</li> </ol> <h2>[WHY]</h2> <ol> <li>]&nbsp;consistency - The point of having style guidelines is to have a common vocabulary of coding so people can concentrate on what you're saying rather than on how you're saying it. We present global style rules here so people know the vocabulary, but local style is also important. If code you add to a file looks drastically different from the existing code around it, it throws readers out of their rhythm when they go to read it. Avoid this ( SRC = google style guide javascript)</li> </ol> <h2>[WHERE]</h2> <ol> <li>] <a href="https://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml" target="_blank">https://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml</a>&nbsp;</li> <ol> <li>] google javascript style guide</li> </ol> <li>] <a href="/view/article?id=2605" target="_blank">javascript MVC style guide</a></li> <ol> <li>] by Alex MacCaw - a few rules for MVC web apps that have served me well and kept large codebases from descending into chaos. While the terminology may differ, these rules should hold true for most client-side MVC frameworks such as Backbone and Ember</li> </ol> <li>]</li> </ol> <h2>[WHEN]</h2> <ol> <li>]</li> </ol> <h2>[EXAMPLE]</h2> <ol> <li>]</li> </ol> <h2>[HOW-TO]</h2> <ol> <li>]</li> </ol> <h2>[REFERENCE]</h2> <ol> <li>]</li> </ol> <h1 style="text-align: center;">&nbsp;</h1>