[Flow] Using aspects to change EmailAddressValidator
Steffen Wickham
steffen at gaming-inc.de
Sat Jan 4 13:05:25 CET 2014
Hello Pankaj,
thanks for your reply! :-)
I would prefer the clean way as described too. But I run in trouble with the EmailAddressValidator while using the ElectronicAddress model. As far as I know the ElectronicAddressValidator use the EmailAddressValidator hardcoded so I don't think it is a suitable way. :-\
Greetings
Steffen
Am 04.01.2014 07:11 schrieb Pankaj Lele <t3pankaj at lelesys.com>:
>
>
> Hello Steffen,
>
> > It is the very first time for me to program in AOP style but the new
> > e-mail validator isn't suitable for me so I will replace it with the old
> > RegEx Validation.
>
> Instead of going into debugging I would rather suggest something clean to you.
> If you want a different EmailAddressValidator then instead of changing the existing EmailAddressValidator using AOP you can develop a new validator itself and use it directly. This would be a clean way.
>
> Happy New Year!
>
> Pankaj Lele,
> Lelesys - http://www.lelesys.com
> Twitter: pankajlele
>
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
More information about the Flow
mailing list