On Wednesday, January 9, 2013 4:34:03 AM UTC+1, weaverryan wrote:
>
> Hi guys!
>
> I'm quite against BC breaks :). I see a decent number of projects, and
> every BC break affects a lot of people. And I think *because* we had so
> many BC breaks on 2.1, we should aim to have as little as possible in the
> future. So, I don't think of it as a "we broke BC in 2.1, so we should be
> able to do more breaks in 2.3". The 2.1 breaks were no fun, so less is
> better!
>
> I agree. I also think that Fabien prefer to see less (or no) BC breaks.
However this seems like a necessary evil to improve the Form component and
we can only break until 2.3 so we should not refrain.
There will be a lot breaks in 2.3:
- The AbstractType class has undergone a major refactoring,
- Form::bindRequest() will be removed in 2.3,
- Some Form events name and namespaces will be removed in 2.3,
- The FormValidatorInterface is deprecated in 2.3 (you'll have to use
events),
- The "validation_constraint" option will be removed in 2.3,
- The "virtual" option will probably be renamed in 2.3,
- "{{ form_enctype() }" might get removed in 2.3,
- ...
I encourage you to search for "deprecated" in the Form component if you
want to get a preview of all the future breaks (The one listed above are
only some of those that will most probably affect "common users").
And as stated in this thread by Bernhard, we could find an acceptable
namespace organization that will most probably have little (or no) impact
on "common users".
This is why I think that rejecting this proposal because it will save one
BC break is not a good argument.
> BUT, changing namespaces is one of these least "scary" breaks you can make
> since it's very easy to find the changes you need to make and it's highly
> unlikely that you will create any hard-to-track-down bugs.
>
> So like my friend Bernhard, I'm a -0... which means nothing I suppose :).
>
> Thanks!
>
> Ryan Weaver
> US Office Head & Trainer - KnpLabs - Nashville, TN
> http://www.knplabs.com <http://www.knplabs.com/en>
> http://knpuniversity.com
> Twitter: @weaverryan
>
>
--
--
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
