Last night I released v 0.71 of Hyrule I thought I would take a couple minutes to walk through a couple of the changes that were made.
So first off we have a bug with the display property. IF you have been paying attention you should of seen a bunch of examples that look kind of like this. When we get an error it will display an error message based on the default message template which looks like "notempty=The field {display} must contain a value.". In the case above it will replace {display} with the @display property. This is all great but what if you don't have a display property. Well what it should do is use the property name. It was not doing this so I fixed that part. Then my friend Tony said why not just humanize the property name. Great idea so thats what we are going to do now. The following will do the same as the example above.
The next problem I came across on my own. Take the following example. Now if you fill nothing in for all 3 properties your going to get back 3 errors. The first 2 because they are still empty and the 3rd because your empty string does not follow the rules of a phone number
This was obviously a problem. What if you just wanted to validate that if the user did enter a phone number that it was valid. It was because of this for validators like phone,ssn,credit card,etc... that we now check to make sure the property is not empty before we validate it. If you want to make sure the phone number has something in it and that its a phone number then you can do the following.
There were some other minor changes but that was the bulk of it. All of the unit tests were also updated to contain a testIsBlankReturnsTrue method. Let me know your thoughts on all of this and feel free to join the Google Group.

#1 by Matt Levine on 5/4/10 - 11:13 PM
#2 by Steve Withington on 5/6/10 - 10:25 AM
Nice job!
@Matt,
See, I told it was gonna be freakin' awesome.
#3 by Mike Henke on 5/17/10 - 10:03 AM
#4 by Dan Vega on 5/18/10 - 11:06 AM