PHP 8.4 support

[beberlei]

This issue tracks all the necessary work for supporting PHP 8.4 in Doctrine.

• Add 8.4 to CI workflow Add CI job for PHP 8.4 #11631
• Prevent use of property hooks in ORM 2, 3.* for now. Prepare PHP 8.4 support: Prevent property hooks from being used #11628
• Add tests with property hooks
• Reasonably sure that reflection abstraction breaks with property hook edge cases [ReflectionPublicProperty](https://github.com/doctrine/persistence/tree/3.3.x/src/Persistence/Reflection due to Internal vs external respresentation storage. (we need to use setRawValue/getRawValue).
• isVirtual properties cannot be mapped to the dabase, ClassMetadata needs to throw exception on this.
• Common Proxy Generator emits a depreecation for 8.4 Add PHP 8.4 support common#1016
• Lazy Objects support Add support for PHP 8.4 Lazy Objects RFC with configuration flag #11853

[zwalden]

Is there somewhere we should be paying attention to see when support for property hooks will be added?

[Kinqdos]

Why did you explicitly disallowed property hooks in v3.3.3. It seem to worked fine with it before. Throwing an exception breaks my code now. Is there a chance to convert this to a warning?

[greg0ire]

Sorry, it was never supposed to be allowed until 3.4.0

[rixafy]

@Kinqdos try changing doctrine/orm version in composer to 3.4.x-dev#bffe56746660f62898455875ada1da86ecf16665 as 3.4.0, it's a commit from my PR #11814 that I'm already using on some projects and it's working fine with property hooks, last rebase with 3.4.x was 2025-03-25, and I think 3.4 will be released soon anyway (and I hope also with that PR).

If it's not working, try latest 3.4.x dev branch if what you are working on allows it, doctrine is pretty stable and well tested even in unreleased versions.

[cjavad]

Has anyone noticed interesting behavior with the proxy generated __sleep functions when using public property hooks for non-doctrine fields on a entity. In particular it looks like "virtual property hooks" are not fully compatible with serialize / unserialize as it has no backing and cannot be saved as so.

[gremo]

I've upgraded to 3.4 stable, but Doctrine is complaining about a hook that isn't even a mapped property. Why?

"Doctrine ORM does not support property hook on App\Entity\Default\CreditMovement::direction without using native lazy objects. Check #11624 for details of versions that support property hooks.

public PaymentFlow $direction {
    get => $this->amount < 0 ? PaymentFlow::Outgoing : PaymentFlow::Incoming;
}

[beberlei]

I've upgraded to 3.4 stable, but Doctrine is complaining about a hook that isn't even a mapped property. Why?

"Doctrine ORM does not support property hook on App\Entity\Default\CreditMovement::direction without using native lazy objects. Check #11624 for details of versions that support property hooks.

public PaymentFlow $direction {
    get => $this->amount < 0 ? PaymentFlow::Outgoing : PaymentFlow::Incoming;
}

Have you enabled native lazy objects? It will not even work for unmapped properties with the old code, that is correct

[gremo]

@beberlei I may have confused enable_lazy_ghost_objects with enable_native_lazy_objects option. Going to test now, thanks!

EDIT: thank you, my bad ❤