He would like to extend it, not to use a completely different one. On Mon, Jun 15, 2009 at 13:17, Marijn Huizendveld<[email protected]> wrote: > > Hi, > > You could just use the sfValidatedFile option > http://trac.symfony-project.org/browser/branches/1.2/lib/validator/sfValidatorFile.class.php#L70 > > Than you could use your own validated file class. > > Kind regards, > > Marijn > > On Jun 13, 2009, at 12:30 PM, Johannes Heinen wrote: > >> >> Hi, >> >> i discovered a really small issue that eventually needs a workaround >> by mastering a few config-files, but in my opinion could be easily >> solved by a little improvement. >> >> The class sfValidatedFile is written in the same file that contains >> sfValidatorFile, which makes it inpossible to extend it by a third >> class if sfValidatorFile.class.php was not previously included (e.g. >> by instanciating sfValidatorFile, so that you take advantage from the >> spl autoload feature). >> >> I would suggest to simply split the source file into 2 class files >> (sfValidatorFile.class.php and sfValidatedFile.class.php), that would >> provide a clean way to instanciate both classes independently and >> without explicit require statements. >> >> What do you think about that? >> >> With best regards, >> de joshi >> >> > > > > > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
