|
Just wondering – would anyone out there be willing to
make some validation improvements and enhancements to reactor for the
community? Specifically, I’m looking to break validation out of the
record objects and into a validation object. I’m thinking the validation objects will, by default
have one method to validate every property of the object. IE.
validateFirstNameLength(UserRecord) validateFirstNameProvided(UserRecord).
These would be grouped into one method per property, validateFirstName(UserRecord).
Then there would be another method, validate(UserRecord) that would call all of
the validateProperty methods. Each of these would accept and return an error
collection. Why? Well, I found out the hard way how restrictive the
validation on records is right now. For example, I’ve had a few case where
a user needs to be validated and either something or something else needs to be
provided based on business rules. Basically somewhere where I wanted to REMOVE
one of the validation routines in the validate method. In that case I had to
copy all of the validate method from the generated object into customizable
object and edit one line of code. Ugh! I’d like to be able to override
validation of one property without touching everything. I figure the record object will still have a validate
method, it would just create a validation object and pass itself into it to
validate itself and it would set the results into the record and return it. (In
case anyone hasn’t noticed records now have methods to see if the object
has been validated or has errors, etc.) Anyone willing to take this on for the betterment of the
community? Doug |
- [Reactor For CF] Volunteers? Doug Hughes
- Re: [Reactor For CF] Volunteers? Paul Kenney
- RE: [Reactor For CF] Volunteers? Doug Hughes
- Re: [Reactor For CF] Volunteers? Paul Kenney

