Skip to content

Add error handling section #78

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 24, 2016
Merged

Add error handling section #78

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ac186ae
Add stuff about strict mode
hollsk Aug 24, 2016
24dc84f
work in existing work from Nature playbook
hollsk Aug 24, 2016
56a03aa
put the IIFE link back :/
hollsk Aug 24, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions languages/javascript.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ Projects should use both [JSHint] and [ESLint] to enforce these rules.
- [Write modules over monoliths](#modules-over-monoliths)
- [KISS](#keep-it-simple)
- [Performant Code](#performant-code)
- [Error handling](#error-handling)
- [Code Style](#code-style)
- [Indentation](#indentation)
- [White Space](#white-space)
Expand Down Expand Up @@ -123,6 +124,17 @@ We should always try to write fast code, but not if it makes the code difficult

If you're writing a small library with a single simple purpose, and you really _really_ need to do it, then it makes sense; in a project with more than one contributor, there's frequently more "cost" than "benefit".

### Error handling

You should assume that your code will fail, and take steps to handle those failures.

Where [ES5 and above is available and strict mode is implemented](http://kangax.github.io/compat-table/es5/), use strict mode: `'use strict';` This causes JavaScript to error early rather than allow malformed or incorrect code to run.

In Node.js, you can add `'use strict';` to the top of each of your source files.

In-browser you should not add your `'use strict';` to the top of the file; instead you should add it to either the file's [IIFE](http://benalman.com/news/2010/11/immediately-invoked-function-expression/) or each defined function if an IIFE isn't present. This is because global strict mode in browsers can cause issues with third-party code.


Code Style
---------

Expand Down