I've just uploaded version 0.85 to validatethis.riaforge.org. I plan
on publishing a blog post detailing all of the changes, but here is a
quick summary. You can also get a quick look at all of the changes in
any release by looking at the changelog.txt file in the distribution.
Here's the summary:
- fixed a bug in ServerValidator.cfc that was causing conditions using
non-numeric DependentPropertyValues to throw an error
- xml files are now allowed to be named .xml.cfm
- xml files can be contained in a folder under the defined
definitionPath folder with the same name as the object type. For
example, if your definitionPath points to /model/, you can put your
user.xml file into either /model/user.xml or /model/user/user.xml.
- you can specify multiple folders in definitionPath in the
ValidateThisConfig structure, and the framework will look in each of
those folders, in the order specified, to find your xml files. For
example, you could set your definitionPath to
"/myapp/model/,/common/model/", and if you ask VT to do something with
a "user" object it will look for the following:
/myapp/model/user.xml
/myapp/model/user/user.xml
/common/model/user.xml
/common/model/user/user.xml
- added a method for getFailuresAsString() to the Result.cfc object
(thanks Craig McDonald)
- made some significant changes to the getInitializationScript() method:
- it no longer requires an objectType to be specified when being called
- it accepts 3 arguments:
- JSLib: the JS library to use - defaults to jQuery
- JSIncludes: boolean to specify whether the scripts to include
the JS libraries should be generated - defaults to true
- locale: the locale - required for i18n
- it no longer requires a context nor a formName
note that these changes have changed the signature of the
getInitializationScript(), which may break backwards compatibility for
anyone already calling that method.
- updated the Coldbox Plugin in the following ways:
- if no setting for VT_definitionPath is defined, it will use the
setting for ModelsPath and the setting for ModelsExternalLocationPath,
in that order, to look for the xml definition files
- added a method called setupValidationSI() which uses the
scriptInclude plugin to load JS into the page. Note that this has been
adapted from a plugin written by Craig McDonald and has not been
tested, as my sample does not make use of the scriptInclude plugin.
If anyone is willing to give it a try and see if it works as expected
that would be great.
I believe that the above changes address all of the outstanding issues
that have been expressed on the list as of late. Please let me know
if you have any remaining issues that you'd like me to address.
Cheers,
Bob
--
Bob Silverberg
www.silverwareconsulting.com