Michael Schoonmaker ed41c51850 Updated Memory.merge to handle null values ... Previously, if the Memory store was merged with an object containing a null value, the following Error occurred: TypeError: Object.keys called on non-object     at Function.keys (native)     at Memory.merge (/.../node_modules/nconf/lib/nconf/stores/memory.js:199:17)     at Memory.merge (/.../node_modules/nconf/lib/nconf/stores/memory.js:200:17)     at Array.every (native)     at Memory.merge (/.../node_modules/nconf/lib/nconf/stores/memory.js:199:29)     at common.merge (/.../node_modules/nconf/lib/nconf/common.js:99:13)     at Array.forEach (native)     at common.merge (/.../node_modules/nconf/lib/nconf/common.js:98:22)     at Array.forEach (native)     at Object.common.merge (/.../node_modules/nconf/lib/nconf/common.js:97:8) This commit prevents that.		2012-09-27 11:26:56 -07:00
..
stores	Updated Memory.merge to handle null values	2012-09-27 11:26:56 -07:00
common.js	make it possible to use other formats than json in common.loadFiles and common.loadFilesSync	2012-09-16 17:45:00 +02:00
formats.js	Surfacing additional JSON.stringify arguments in formats.json.stringify, and adding the json_spacing option to the File constructor.	2012-04-13 13:22:42 -07:00
provider.js	[fix] null values should merge properly instead of throwing errors	2012-09-08 20:10:58 -05:00