Re: QF3.2 - 2 BC breaks with custom method!
| From: | Ignatius Reilly | Date: | Wed, 05 Nov 2003 22:01:00 +0000 |
| Subject: | Re: QF3.2 - 2 BC breaks with custom method! | ||
| References: | 1 2 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-8795@lists.php.net to get a copy of this message | ||
Thanks to all. Very informative.
Bertrand and Alexey's suggestion looks powerful. I will give it a try.
Regards
Ignatius
_________________________
"Lukas Smith" <smith@backendmedia.com> wrote in message
news:php.pear.general-8792@news.php.net...
> > From: Alexey Borzov [mailto:borz_off@cs.msu.su]
> > Sent: Wednesday, November 05, 2003 10:24 PM
>
> > Ignatius Reilly wrote:
> > > OK. I struggled to upgrade to 3.2
> > > The validation of custom functions seems to suffer at least two BC
> > breaks:
> >
> > Er, when we said that we preserved backwards compatibility, we couldn't
> > imagine
> > all possible clever solutions existing out there. ;]
> >
> > I already wrote something like this in private to Hodicska Gergely who
> > complained about related problems, but I think it wouldn't hurt to
repeat
> > this
> > in the list.
> >
> > The problem with your approach is: QuickForm's validation was designed
to
> > validate the *value*, not the *element*.
>
> Just as a quick FYI without knowing any of the details:
> Having complete docs for packages helps for deciding what a BC break is
and
> what isn't.
>
> Removing undocumented features is not a BC break!
>
> IIRC quickforms is quite well documented.
>
> Regards,
> Lukas