Have you seen Sean Corfields validation examples in the article.cfc on his
site? It is a bit of work to set up for the first component but then it's
pretty fast to duplicate and modify to suit different objects. You might
save yourself some work in this example if you just ask for the birthdate
and calculate age. A few things i've read recently point out that it makes
much more sense to calculate age, as age changes over time.
Also, IMO, i don't think you need to place these values in variables
(MaxNameLength) - just set them as var's in your validation method if you
don't need them available anywhere else. That will also help to reduce the
bloat.
Modified from Sean's article.cfc example:
cfset var maxNameLength = 50
<cfif NOT structKeyExists(variables.instance,"name") OR
Len(variables.instance.name) GT maxNameLength OR
Len(variables.instance.name) EQ 0>
<cfset valid = false />
<cfset variables.invalidFields =
listAppend(variables.invalidFields,"name") />
</cfif>
You could do something similar for birthdate between Now() and 120 years ago
and you'd be all set with only 2 if statements. But no need to set these
values in the variables scope unless they are really needed by other
functions in the component. That'll just create unnecessary clutter.
I'm having fun with the validation routines i have working. It's cool how
clean it is once you have it set up.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Jon Gunnip
> Sent: Friday, November 28, 2003 9:05 PM
> To: [EMAIL PROTECTED]
> Subject: [CFCDev] Exposing Validation rules for a component
>
>
>
> Hello All,
>
> I am wondering how/whether I should expose data validation
> information for arguments passed into my components.
>
> Let us assume that I have a Person component that stores a name
> and age. At the top of the component I am defining:
>
> Variables.MinNameLength = 1;
> Variables.MaxNameLength = 50;
> Variables.MinAge = 0;
> Variables.MaxAge = 120;
>
> These variables are used in a Validate() routine inside the
> component to make sure the instance values passed to a
> Person.Create() or Person.Update() are in a valid range.
>
> I also have public functions in the Person component such as
> GetMinNameLength(), GetMaxNameLength(), GetMinAge(), GetMaxAge()
> that return the appropriate values. The idea is that the web
> pages that accept input for a call to Person.Create() or
> Person.Age() can easily call these GetMin(), GetMax() functions
> to create things like JavaScript validation or to set the size
> attribute of text input fields. Thus, bad input data can be
> caught before it is passed to the Person component.
>
> If the valid length of an allowable name changes, I then need to
> change the validation variables at the top of my component (and
> probably the size of a database field), but not the web forms
> that use the component.
>
> Does this seem like a good model? Is it too granular?
>
> It is definitely adding a lot of functions (and coding time) to
> my components!
>
> Thanks,
> Jon
>
> ----------------------------------------------------------
> You are subscribed to cfcdev. To unsubscribe, send an email
> to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev'
> in the message of the email.
>
> CFCDev is run by CFCZone (www.cfczone.org) and supported
> by Mindtool, Corporation (www.mindtool.com).
>
> An archive of the CFCDev list is available at
www.mail-archive.com/[EMAIL PROTECTED]
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
