Bug #87773
closed
ClassSchema doesn't treat unsignated classes anymore
0%
Description
with #87632, the default value from ClassSchema was changed from Entity to zero, but this causes ClassSchema to not treat disguised ValueObjects anymore.
With the change applied, TYPO3\CMS\Belog\Domain\Model\Constraint is not handled anymore and causes the BE Log Module to fail with
InvalidArgumentException
There is no @var annotation for property "userOrGroup" in class "TYPO3\CMS\Belog\Domain\Model\Constraint".
Setting the default value in ClassSchema to 1 (Value Object) also omits the expensive followup relation resolving, but brings back the class schema resolving for classes not explicitely extending AbstractValueObject.
Updated by Anja Leichsenring about 5 years ago
- Related to Bug #87632: Do not treat all classes as entities added
Updated by Gerrit Code Review about 5 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/59793
Updated by Gerrit Code Review about 5 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/59793
Updated by Gerrit Code Review about 5 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/59793
Updated by Susanne Moog about 5 years ago
- Status changed from Under Review to Closed
Patch was abandoned as original patch was reverted.
Updated by Riccardo De Contardi about 5 years ago
- Assignee deleted (
Anja Leichsenring)