Gary Wilson wrote: > What do you think about adding a ValidationError similar to > CriticalValidationError but one that would stop further evaluation of > _all_ validators in the manipulator instead of just the remaining > validators for the current form field being processed?
It's not an error, it's a directive to the engine to stop downstream work: raise StopValidating Personally I don't like it when installed components have the ability to blow up the containing code /by design/. There's that. There's also introduction co-concurrence constraints in validators, where validators depend on other validators being ahead of them to for gigo reasons and validators are designed to blow up because they 'know' downstream components are going to be fragile or not doing useful work - imo it lowers overall robustness. I'd argue the validators teed up this way aren't cohesive and should be coupled together - either use a strategy pattern, or nested pipelines*. cheers Bill * the validation engine loads one validator, but it's made up of one or more valdiations which natually belong together and can be locally optimised. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
