ClassCacheManager merge generates duplicate initializeObject() in tx_news_domain_model_news.php

[can0199]

Bug Report

Current Behavior
When extending GeorgRinger\News\Domain\Model\News via
$GLOBALS['TYPO3_CONF_VARS']['EXT']['news']['classes'] and defining initializeObject() in the extending class, TYPO3 crashes with:

Fatal error: Cannot redeclare GeorgRinger\News\Domain\Model\News::initializeObject() in var/cache/code/news/tx_news_domain_model_news.php

The generated proxy class contains initializeObject() more than once.

Expected behavior/output
Extending the News model with its own initializeObject() should not produce duplicate method declarations in the generated proxy class.
A single valid merged initializeObject() method (or another safe conflict handling) is expected.

Environment

• TYPO3 version(s): 14.1
• news version: 14.0.1
• Is your TYPO3 installation set up with Composer (Composer Mode): yes
• OS: Linux 6.8.0-64-generic with ddev

Possible Solution
Adjust ClassCacheManager add exception in merging for the function initializeObject() similar to the logic for __construct function

Additional context
I believe this problem was introduced when this PR was merged: #2722

[kitzberger]

Can confirm this for TYPO3 13 and EXT:news 13.0.2 and that the PR is fixing that issue for version 13 as well. Thanks!

Since the topic "n:m relationship" isn't covered in https://docs.typo3.org/p/georgringer/news/main/en-us/Tutorials/ExtendNews/ProxyClassGenerator/Index.html I've created a PR for that: #2802

I reckon that once #2786 is merged the docs should be enhanced again, by mentioning initializeObject().