property for which no validations are defined throws an exception #1323

Merged
merged 1 commit into from Nov 18, 2014

Conversation

Projects
None yet
2 participants
@gsmeets
Contributor

gsmeets commented Nov 10, 2014

I created a small fix for the edge case when you explicitly test a property for errors when there are no validations defined in the can.Map.

attrs would be filled with your one property that is checked, but validations would be undefined, causing an issue.

gsmeets
Fixed issue where validations tripped on a non-exinstant property on the
map when specifically testing for errors on that property name.

@daffl daffl added this to the 2.1.4 milestone Nov 18, 2014

daffl added a commit that referenced this pull request Nov 18, 2014

Merge pull request #1323 from gsmeets/map-without-validations-crashes…
…-on-errors

property for which no validations are defined throws an exception

@daffl daffl merged commit 7e0b2cc into canjs:master Nov 18, 2014

1 check passed

continuous-integration/travis-ci The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment