Project

General

Profile

Actions

Bug #87773

closed

ClassSchema doesn't treat unsignated classes anymore

Added by Anja Leichsenring over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2019-02-24
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

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.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #87632: Do not treat all classes as entitiesClosedAlexander Schnitzler2019-02-04

Actions
Actions

Also available in: Atom PDF