[TASK] Better document extbase defaultQuerySettings behavior
Extbase tends to become a victim of its own magic. In this case, whenever a repository method like initializeObject() uses setDefaultQuerySettings(), it fully overrides potentially useful settings created by the factory. Developers struggle here since all of a sudden things like storagePid restrictions from configuration are no longer applied. We can't change this behavior easily - it would require some awful dirty handling in QuerySettingsInterface, leading to even more opaque complexity in this area. The change adds comments to the property and the setter hinting about the behavior. Resolves: #89295 Releases: master, 10.4 Change-Id: I3b99dfa6d5a7881caaa952672386c00ebfa0166c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69324 Tested-by:Oliver Bartsch <bo@cedev.de> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Christian Wolff <chris@wolffc.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
Please register or sign in to comment