Feature #3163
Organize validator code consistently
Status: | New | Start date: | ||
---|---|---|---|---|
Priority: | Low | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | |||
Target version: | - | |||
Sponsored: | Tested version: |
Description
Peter suggested me to establish a common place for qubit validators. For the time being we have:
lib/QubitValidatorCountable.class.php
plugins/sfIsadPlugin/lib/QubitValidatorIsadDates.class.php
I am not sure if the second one is definitive.
[g] Legacy categories: Form validation
History
#1 Updated by Jesús García Crespo over 12 years ago
- Target version set to Release 1.1
[g] Labels added: Type-Enhancement, Milestone-Release-1.1, Component-Validation
[g] Labels removed: Type-Defec
#2 Updated by Jesús García Crespo over 12 years ago
Probably, lib/ is a good place, but if we are goint to need many validators,
lib/validators could be a better place following the organization used by symfony code.
#3 Updated by Peter Van Garderen over 12 years ago
if we have validators that are specific only to a certain standard then I think it
should be stored within plugins/sfStandardXPlugin/lib (e.g. when checking for Level
of Description rules that are specific only to ISAD or RAD). All other validators
should go into /lib for now. Since there will be several of these I would prefer to
have those in a /lib/validators directory as Sevein suggests. The opposite is also
true, some /plugins validators are actually generic and applicable to other standards
(i.e. the date range validator) these should be moved out of /plugins and into
/lib/validators. The other issue is moving validator logic out of /action code and
into an appropriate validator class of its own (e.g. ISAD level of description
validation logic is in sfIsadPlugin/actions/showAction.class.php.
#4 Updated by Peter Van Garderen over 12 years ago
- Subject set to Organize validator code consistently
#6 Updated by Evelyn McLellan over 11 years ago
- Target version set to Release 1.2
Moved to 1.2.
[g] Labels added: Milestone-Release-1.2
#7 Updated by David Juhasz over 10 years ago
- Target version set to Release 1.3
Roll over to Release 1.3
[g] Labels added: Milestone-Release-1.3
#8 Updated by Dan Gillean almost 7 years ago
- Project changed from Access to Memory (AtoM) to AtoM Wishlist
Moving to AtoM Wishlist subproject until sponsored for inclusion or taken on by Artefactual developers.
#9 Updated by Jesús García Crespo almost 7 years ago
- Assignee deleted (
Jesús García Crespo)