-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Merge 3.3.x into 4.0.x #11650
Merged
Merged
Merge 3.3.x into 4.0.x #11650
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…2.20.x_0oKsBvVN Merge release 2.19.7 into 2.20.x
When adding the same lifecycle event callback to two or more lifecycle events, the generator will create a stub for each event resulting in fatal 'Cannot redeclare' errors. That is, only if the callback name contains uppercase letters.
* 2.19.x: Make nullable parameters explicit in generated entities (doctrine#11625) Update attributes-reference.rst Bump doctrine/.github from 5.0.1 to 5.1.0 (doctrine#11616) Move orphan metadata to where it belongs PHPStan 1.12 (doctrine#11585)
* 2.19.x: Replace custom directives with native option
For now doctrine/common generates proxies that trigger deprecation, so let us only test with lazy ghosts only.
E_STRICT is deprecated as of PHP 8.4
Add CI job for PHP 8.4
…rine#11628) Prevent property hooks from being used as they currently would work on external non-raw values without explicit code.
People that might have experimented with property hooks while still using ORM < 2.20.0 need to know that they need to remove their experiment or upgrade to a version that explicitly supports them.
* 2.19.x: PHPStan 1.12.6 (doctrine#11635)
* 2.19.x: PHPStan 1.12.6 (doctrine#11635)
* 3.2.x: PHPStan 1.12.6 (doctrine#11635)
…)` method (doctrine#11641) We use this method only from within one of our own test cases, and I don't see how it would be useful to anybody else outside – it has to be called on the `Parser` instance which exists internally in the `Query` only. Deprecating and removing it in 3.x allows for a slight simplification in the `Parser` there, since we do no longer need the field (it can be a local variable).
* 2.20.x: Stop recommending vendor-prefixed PHPDoc (doctrine#11640) Let PHPStan detect deprecated usages (doctrine#11639) Add upgrade note about property hooks (doctrine#11636) Prepare PHP 8.4 support: Prevent property hooks from being used (doctrine#11628) Use E_ALL instead of E_ALL | E_STRICT Add CI job for PHP 8.4 fix generating duplicate method stubs
* 3.3.x: Stop recommending vendor-prefixed PHPDoc (doctrine#11640) Let PHPStan detect deprecated usages (doctrine#11639) PHPStan 1.12.6 (doctrine#11635) Add upgrade note about property hooks (doctrine#11636) Prepare PHP 8.4 support: Prevent property hooks from being used (doctrine#11628) Use E_ALL instead of E_ALL | E_STRICT Add CI job for PHP 8.4 fix generating duplicate method stubs
* 2.20.x: Remove vendor prefix of PHPDoc referencing class-string (doctrine#11643) Deprecate the `\Doctrine\ORM\Query\Parser::setCustomOutputTreeWalker()` method (doctrine#11641)
* 3.3.x: Remove vendor prefix of PHPDoc referencing class-string (doctrine#11643) Deprecate the `\Doctrine\ORM\Query\Parser::setCustomOutputTreeWalker()` method (doctrine#11641)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.