Conditional validations fail when given multiple properties to validate
Reported by ronin-41351 (at lighthouseapp) | February 12th, 2009 @ 09:13 AM | in 0.10.0
Here is an example:
This will fail, but this will work:
Comments and changes to this ticket
-
Dan Kubb (dkubb) February 21st, 2009 @ 02:49 AM
- Assigned user set to “Michael Klishin (antares)”
-
Michael Klishin (antares) March 24th, 2009 @ 02:01 PM
- State changed from “unconfirmed” to “accepted”
-
Dan Kubb (dkubb) March 24th, 2009 @ 03:04 PM
- State changed from “accepted” to “resolved”
(from [b79bae17f22f40cc81fdfd87322c5b649de478e7]) [dm-validations] Make it possible to list arbitrary number of fieds and confition clause
- Makes the following case works as expected: http://pastie.org/387074, so you don't have to do http://pastie.org/387093 any more
- It is a good principle to live by, always duplicate options passed to a method when you pass them along
[#801 state:resolved] http://github.com/datamapper/dm-...
-
Michael Klishin (antares) March 24th, 2009 @ 03:05 PM
- Milestone set to “0.10.0”
Will be in for 0.10, see b79bae1 in dm-more (currently on next branch). Thanks for reporting.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
People watching this ticket
Dan Kubb (dkubb)
Michael Klishin (antares)
Tags
Referenced by
-
801
Conditional validations fail when given multiple properties to validate
[#801 state:resolved]
http://github.com/datamapper/dm-...