I am getting ready to do a release candidate for version 1.0
Bob Silverberg
I decided that, rather than continuing to hold out on a 1.0 until I
can get all of the new features into the fw that I'd like to have
there, I should just get 1.0 out there, and then add features later.
There was one thing that I did want to address prior to 1.0, which I
have just completed, and that is to have the default generated failure
messages be the same on the client and the server. The text for those
is now being drawn out of a resource bundle, which is also doing text
replacement for the parameters.
For those Git fans of you, the lastes version is sitting in the
"develop" branch, and I have also uploaded a zip file of what will be
the final distribution for 1.0RC1 at
https://github.com/downloads/ValidateThis/ValidateThis/ValidateThis-1.0RC1.zip.
As I did make some significant changes to a lot of files for the
enhancement, I would really appreciate it if some of you could take a
few minutes to download the latest and let me know if you run into any
problems with any of the apps you are using it with. Also, for any of
you using custom SRVs and CRSs, they should continue to work fine as
is, but you may want to upgrade them to get their default messages
from resource bundles as well. Let me know if you are in that boat
and I'll try to put together some docs on how to do that.
I'm going to try to update the online docs over the next few days,
with the aim of releasing this by the end of the week.
Here's what the changelog says about the updates in this version:
- removed the query.validate.pack.js file as it is no longer provided
by the plugin author - users pointing directly to that file will have
to point to query.validate.min.js instead
- generated failure messages are now being pulled from the file
/ValidateThis/locales/en_US.properties, for both client and server
- added support for optionality in client rule scripters that required it
- added Qunit tests for CRSs
- performance improvements to the JavaScript generated for client-side
validations
- edited getValidator to allow it to search components dot-path under
definitionPath e.g model.entity.User ->
/mydefinitionPath/mode/entity/User.xml
- added an ignoreMissingProperties argument to the validate() method
which defaults to false
- fixed a bug which caused recursive failure information to be added
to the Result object
- converted Selenium end-to-end tests to use CFSelenium
- fixed bug where the client daterange validator did not ignore blank fields
- fixed bug where the desc attribute was ignored if it was the same as
the name attribute.
- added an ANT build file
- fixed issue #26 - addressed issues with the use of $ in CRSs
- fixed issue #17 - replaced use of local struct with var scope
- added custom inheritance checking to work around significant
performance problem with the CF in-build isInstanceOf()
- fixes for case-sensitivity issues of ValidateThis folder
- now using protocol-agnostic URLs to pull in scripts from CDN
- added project README.md file
- changed links in sample apps to be relative
Let me know if anyone runs into any problems.
Thanks,
Bob
--
Bob Silverberg
www.silverwareconsulting.com