test(doctrine): uninitialized typed properties in PersistProcessor

[Copilot]

This PR adds a functional test to verify the fix for issue #7735, which was already implemented in PR #7738. The fix prevents fatal errors when PersistProcessor::handleLazyObjectRelations() attempts to access uninitialized typed properties in entities that use Doctrine lifecycle callbacks.

Background

PersistProcessor::handleLazyObjectRelations() was calling ReflectionProperty::getValue() without checking initialization state, causing fatal errors when entities use typed properties initialized in Doctrine lifecycle callbacks. This occurs before persist() executes, so @PrePersist callbacks haven't run yet.

The fix (adding an isInitialized() guard before getValue()) was merged in PR #7738.

Changes

• Add functional test Issue7735Test with entity using typed property initialized in @PrePersist
• Add test fixtures: Issue7735Entity and Issue7735Resource using ObjectMapper
• Complements the unit test from PR fix(doctrine): skip uninitialized properties in handleLazyObjectRelations #7738 with end-to-end verification

Example

#[ORM\Entity]
#[ORM\HasLifecycleCallbacks]
class MyEntity
{
    #[ORM\Column]
    private string $generatedValue; // Uninitialized - causes fatal on getValue()

    #[ORM\PrePersist]
    public function prePersist(): void
    {
        $this->generatedValue = 'generated_' . uniqid();
    }
}

Previously this crashed with "Typed property must not be accessed before initialization". Now the property is skipped until after persistence when it's initialized.

Original prompt

Fix issue #7735 on branch 4.2.

Context:

• PersistProcessor::handleLazyObjectRelations() iterates entity properties and calls ReflectionProperty::getValue() without checking ReflectionProperty::isInitialized().
• When entities use typed properties that are only initialized in Doctrine @PrePersist callbacks, handleLazyObjectRelations() runs before EntityManager::persist(), so properties may be uninitialized and PHP fatals: Typed property ... must not be accessed before initialization.
• This affects ObjectMapper-enabled operations where $operation->canMap() is true.

Required changes:

1. In PersistProcessor::handleLazyObjectRelations(), add a guard:

   • If !$reflectionProperty->isInitialized($data), skip/continue before calling getValue().
   • Keep existing behavior for identifiers and non-object values.

2. Read and follow repository instructions in AGENTS.md (note: file is uppercased).

3. Add a functional test under tests/Functional following existing conventions.

   • The test should reproduce the crash scenario: a Doctrine entity with typed properties that are not initialized until @PrePersist.
   • The resource should be ObjectMapper-enabled (Map usage) so canMap() is true.
   • Perform a POST request that previously triggered the fatal error.
   • Assert the request succeeds (e.g., 201) and that the response is valid (at minimum contains created resource data). Ensure the test would fail on current code (fatal) and pass with the fix.

4. Open a pull request against api-platform/core with base branch 4.2.

Notes:

• Current user login is soyuka.
• Ensure code style and test conventions match the repo.

This pull request was created from Copilot chat.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[soyuka]

#7738 got merged rebase and keep the functional test.

[Copilot]

#7738 got merged rebase and keep the functional test.

Rebased on 4.2 (commit 4f307d3). The functional test is preserved in commit cf31875.