-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Form] Possible bug in \Symfony\Component\Form\ResolvedFormType #14919
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@c1tru55 please submit PRs to the |
@c1tru55 you should submit your PR to the oldest supported branch that you can reproduce this bug on. We merge older branches to the newer ones regularly. |
@jakzal it seems that this bug exists in all branches starting from 2.3, so I made PR to 2.8 |
2.4 is not supported. I think the bug is still present in 2.3, no? However, even if you send a PR to 2.8, we can still merge it to 2.3. So don't worry about it too much. |
This is already fixed #14896 |
2.4 has reached EOM: https://symfony.com/roadmap.json?version=2.4 |
When I try to call
ResolvedFormType::getTypeExtensions()
I get an error:As I see there are code for BC ( https://github.com/symfony/Form/blob/master/ResolvedFormType.php#L98 ):
but we don't have
use
statement for deprecated AbstractType:so it is assumed that deprecated AbstractType class is stored in the same folder as ResolvedFormType class. But current AbstractType is also stored in the same folder with ResolvedFormType and it doesn't have
getExtensions()
method: https://github.com/symfony/Form/blob/master/AbstractType.phpThe text was updated successfully, but these errors were encountered: