On Monday, January 7, 2013 1:57:07 PM UTC+1, Matt Robinson wrote:

> 0.
>
> Well, 0.5, just to be awkward :). If BC's going to break substantially 
> anyway (which afaik, it's not, so ignore the rest of this sentence), we 
> should take the opportunity to reorganise the code purely as a matter of 
> taste, to make it more consistent with the other Symfony components. 
>
> I don't think it's particularly fair to say "there has already been 
> countless BC breaks in the Form component" either. Hasn't there really just 
> been one (admittedly major) one between 2.0 and 2.1? I don't think removing 
> the legacy classes in 2.3 counts as a pending BC-break; that's just 
> leftovers from the previous BC-break, isn't it?) I also don't really accept 
> that reorganising will noticeably ease maintenance. 
>

You can count the BC break from 2.0 to 2.1 in 
https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Form/CHANGELOG.md
.

No 2.2 BC are listed (yet) because most of them are hidden by legacy 
classes but go grep for @deprecated in the Form component, you'll find 
quite a lot of "future" (ie 2.3) BC breaks.

Regarding maintenance, what's your experience with debugging/extending the 
Form component ?

And don't get me wrong, I don't say that we should never break BC - If it 
could improve the component, it's a go while we have the opportunity to do 
so (ie pre-2.3) !
 

>
> TL;DR: it's not great as it is, but it's hardly awful. If there were no 
> more changes until 3.0, I think I'd count my blessings rather than my 
> regrets :)
>

It seems we don't have the same opinion here. Do not hesitate to submit 
issues if you see things that can be improved. It will be too late in 6 
months.
 

> --
> Matt Robinson
> https://lazycat.org/
>

Victor 

>  
>

-- 
-- 
If you want to report a vulnerability issue on Symfony, please read the 
procedure on http://symfony.com/security

You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en


Reply via email to