Steev Hise steevhise

JSON.stringify(this, groupFields).replace(/"([^"]+)":/g, '$1:');

To list branches with commits not merged into master:

git branch --no-merged master

To list the relevant commits:

git cherry -v master <branch>

To see both local and remote: git branch -a --no-merged master

Whether you use 2 spaces or 4 spaces, there are a few simple things that can make your node.js code easier to read. We've been using them in all the hapi modules for over 4 years now to great results. This list is by no means complete but it highlights the most useful elements that will give you immediate value in reducing bugs.

Required modules

JavaScript makes it harder than most languages to know where variables are coming from. Variables assigned required modules are particularly important because they represent a singleton object shared with the entire application. There are also globals and module globals, along with function variables and arguments.

Traditionally, variables starting with an uppercase letter represent a class that must be instantiated using new. This was an important semantic in the early days of JavaScript but at this point, if you don't know Date requires new Date() you are probably very new. We have adopted Upper Camel Case variable names for all module global variables

	# get the list of audio devices
	pactl list
	pactl set-defaut-sink <device name> # set the output device
	pactl list sources\|sinks # list the outputs or inputs
	pactl load-sample <sound file>
	pactl list-samples # get list of loaded sound samples
	pactl play-sample <sample name>

	# pipe from input to output
	arecord \| aplay


	/**
	* fc-filestystem-loader
	* This custom Swig template loader does 2 things differently from the regular Swig filesystem loader:
	* 1. missing template files return an error string rather than throwing an error
	* 2. if file isn't found in default place, looks in the "IncludeDir" (for common partials)
	*
	*/

	let target;