👍

Well, I am not actually sure my PR should be merged, as I see thatAbstractType still makes use of theOptionResolverInterface.
I am going to propose a PR on the Symfony repository to remove this reference.

@michaelperrin The reference can only be removed in 3.0 as it would breack BC otherwise.

@xabbuh This is what I was thinking about, many libraries would get broken as PHP would raise an error on the declaration ofsetDefaultOptions.

Well, this PR was not a good idea! Before closing it, I have a question. Is themaster branch ofsymfony-docs repository corresponding to the docs of Symfony 3.0?
In that case, this PR can be reopened on themaster branch in caseOptionsResolverInterface is removed from themaster branch of Symfony as well.

@michaelperrin Yes, branches of the documentation and the code repositories are the same.

see alsosymfony/symfony#12782

Alright then, I think i can propose a PR on themaster branch of Symfony that removes theOptionsResolverInterface (Hi@webmozart !) and then this PR will make sense.

It seems that the removal of deprecated stuff on Symfony 3 hasn't started yet, but maybe it's already time to prepare it.

It seems that the removal of deprecated stuff on Symfony 3 hasn't started yet, but maybe it's already time to prepare it.

Actually, it has already started

Ok then, so I can do it on theOptionsResolverInterface

As I pointed this out in the symfony repository I think we should find a way to have an upgrade path without depreciation notices on the form types as well.

There are several possible approaches I can think of, but I think we should await feedback from@webmozart how he wants to have it. Currently in the master branch relies still on the interface.

https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Form/AbstractType.php#L45

Thanks for opening this (and@peterrehm for the issue on the core code). This is indeed awkward! For now, I'm going to wait for the core solution to this. As far as the docs go, if I understand everything correctly, theonly thing that we can recommend that is functional is the deprecatedOptionsResolverInterface, correct?

If I'm mistaken and thereare some changes that can be made now, let me know!

Thanks!

I have just provided an PR which might resolve that issue, but I think it can only be resolved for 2.7, even though I think it should go into 2.6. (symfony/symfony#12891)

Currently I do not see any workaround on this behavior.