Remove deprecated methods from ParserResult and the SingleSelectExecutor class#12195
Remove deprecated methods from ParserResult and the SingleSelectExecutor class#12195mpdude wants to merge 1 commit intodoctrine:4.0.xfrom
ParserResult and the SingleSelectExecutor class#12195Conversation
9a68fbf to
e02d232
Compare
greg0ire
left a comment
There was a problem hiding this comment.
Please add something in UPGRADE.md
ParserResultParserResult and the SingleSelectExecutor class
|
The PHPStan baseline needs an update: Lines 2319 to 2323 in cdc52b2 |
41d021f to
1814d10
Compare
1814d10 to
ac45a1c
Compare
|
fixed |
|
Moar conflicts 😭 |
ac45a1c to
8f95375
Compare
|
Needs |
75c0189 to
c5c66e5
Compare
I'm not sure I agree… did you remove this test because it broke? If yes, there should be instructions in UPGRADE.md explaining what's needed to update from 3 to 4… clearing a cache, I guess. |
|
IIRC yes – unserializing an old (2.x) ParserResult caused a notice, since it contained fields that now are no longer present in the class. I'll definetly add an upgrade notice. |
…ecutor` class This removes methods that have been deprecated in 2.20.x via doctrine#11188 and/or got deprecation notices added in doctrine#12196.
c5c66e5 to
713c985
Compare
|
Should I do anything else here? |
|
I'd like to get @derrabus 's opinion on this. |
|
Also, this needs a rebase. |
|
There hasn't been any activity on this pull request in the past 90 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. |
| The internal structure of `Doctrine\ORM\Query\ParserResult` changed. Thus, it is no longer possible to unserialize cached parser result instances that | ||
| were created and serialized with the previous major version of the ORM. |
There was a problem hiding this comment.
Is it possible to create a compat layer?
This removes methods that have been deprecated in 2.20.x via #11188 and/or got deprecation notices added in #12196.