I am on other side. Whatever we would need for any basic operation should be part of any framework.
Form validation process is a very common for almost every project regardless of being small or big. I believe it should be part of any level of framework. Or there would be a simple way for plug&play usage as a validation plugin.
In Luis’ announcement he stated: “ColdBox LITE is basically ColdBox MVC only.”
Validation is not any part of MVC, and therefore should absolutely not be part of ColdBox LITE.
There are a number of validation frameworks that can be plugged right in, including ColdBox validation. Let the developer decide which validation framework is right for their application.
Again, validation is not a concern of MVC. Let the MVC framework be the best at its job, and leave it to the developer to determine which validation framework is best for that job.
In my opinion, I don’t think so. Some folks may want to have their own validation framework/libraries or method in place causing redundancy if CB Lite already contains it.
Have you considered perhaps a method for folks to pick their libraries from (core, extras, plugins, even maybe options from forgebox) like an “a la carte” interface and building it on the fly? (not that you are not busy already! )
Yes, that is the way we will go on this. We are arleady in discussions of how to use this new mvc as our base for extension for the platform which will include all pieces. However, as of now cbl will easily be able to add the following to the mix: