Issue Bug Closed

#87773ClassSchema doesn't treat unsignated classes anymore

Anja Leichsenring 02/24/19, 08:39 updated 03/01/19, 22:58

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.

Reviews 1