-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
removed some Form related deprecation notices #15711
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
Conversation
👍 |
d80dd2e
to
fed9cf4
Compare
I've fixed some more thanks to Silex. |
👍 Status: Reviewed |
Some tests are failing though |
yeah, tests checking these methods explicitly. they should be updated for the new returned value. and we should probably write integration tests for these classes (using the FormIntegrationTestCase), to run the extension code from a form factory as this is where deprecations are triggered |
fed9cf4
to
4253824
Compare
This PR was merged into the 2.8 branch. Discussion ---------- removed some Form related deprecation notices | Q | A | ------------- | --- | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | n/a | License | MIT | Doc PR | n/a This removes a deprecation notice. Commits ------- 4253824 removed some Form deprecation notices
We only enforce version 2.8 or higher of the Form component for tests in the FrameworkBundle. Shouldn't we first check the installed version of the Form component (alternatively we could add a conflict rule, but that doesn't seem to be the best solution to me)? |
see #15721 |
…versions (xabbuh) This PR was merged into the 2.8 branch. Discussion ---------- [FrameworkBundle] compatibility with older Form component versions | Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #15711 | License | MIT | Doc PR | Commits ------- 01ad767 compatibility with older Form component versions
This removes a deprecation notice.