Fixed issue where validations tripped on a non-exinstant property on the

map when specifically testing for errors on that property name.
afaden · Nov 10, 2014 · 398f2df · 398f2df
1 parent 7aa6456
commit 398f2df
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/map/validations/validations.js b/map/validations/validations.js
@@ -160,11 +160,11 @@ steal('can/util', 'can/map', function (can) {
 							errors[attr].push(res);
 						}
 					});
-				}, validations = this.constructor.validations,
+				}, validations = this.constructor.validations || {},
 				isTest = attrs && attrs.length === 1 && arguments.length === 2;
 			// go through each attribute or validation and
 			// add any errors
-			can.each(attrs || validations || {}, function (funcs, attr) {
+			can.each(attrs || validations, function (funcs, attr) {
 				// if we are iterating through an array, use funcs
 				// as the attr name
 				if (typeof attr === 'number') {

diff --git a/map/validations/validations_test.js b/map/validations/validations_test.js
@@ -343,4 +343,8 @@ steal("can/map/validations", "can/compute", "can/test", function () {
 		task.attr('age', 'bad');
 		task.attr('age', 'still bad');
 	});
+	test('Validate undefined property', function () {
+		new can.Map().errors( "foo" );
+		ok(true, "does not throw" );
+	});
 });