10000 removed some Form related deprecation notices by fabpot · Pull Request #15711 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

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

Merged
merged 1 commit into from
Sep 8, 2015

Conversation

fabpot
Copy link
Member
@fabpot fabpot commented Sep 7, 2015
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.

@TomasVotruba
Copy link
Contributor

👍

@fabpot fabpot force-pushed the deprecation-notice-form-type branch from d80dd2e to fed9cf4 Compare September 7, 2015 16:57
@fabpot fabpot changed the title removed a deprecation notice removed some Form related deprecation notices Sep 7, 2015
@fabpot
Copy link
Member Author
fabpot commented Sep 7, 2015

I've fixed some more thanks to Silex.

@Tobion
Copy link
Contributor
Tobion commented Sep 7, 2015

👍

Status: Reviewed

@nicolas-grekas
Copy link
Member

Some tests are failing though

@stof
Copy link
Member
stof commented Sep 7, 2015

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

@fabpot fabpot force-pushed the deprecation-notice-form-type branch from fed9cf4 to 4253824 Compare September 8, 2015 05:19
@fabpot fabpot merged commit 4253824 into symfony:2.8 Sep 8, 2015
fabpot added a commit that referenced this pull request Sep 8, 2015
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
@xabbuh
Copy link
Member
xabbuh commented Sep 8, 2015

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)?

@xabbuh
Copy link
Member
xabbuh commented Sep 8, 2015

see #15721

fabpot added a commit that referenced this pull request Sep 25, 2015
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants
0