Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] TYPO3 12: AbstractUuidAwareObjectTypeConverter::setParentObjectAndProperty: "Return value must be of type mixed, none returned" exception #32

Open
3l73 opened this issue Sep 3, 2024 · 0 comments

Comments

@3l73
Copy link

3l73 commented Sep 3, 2024

The abstract class AbstractUuidAwareObjectTypeConverter implements the PimBasedTypeConverterInterface.
The method setParentObjectAndProperty() should as defined in the interface return mixed data.
However, the method returns nothing which leads into the exception "Return value must be of type mixed, none returned"

Expected behaviour

Call of the method setParentObjectAndProperty() does not lead to an exception

To Reproduce

  1. Call the method setParentObjectAndProperty() within your code.

Used versions:
TYPO3: v12.4.17
Extension version: 3e00a60 (@Dev-Master)

Additional context

The interface PimBasedTypeConverterInterface defines the method setParentObjectAndProperty() with the return type mixed.

public function setParentObjectAndProperty(AbstractEntity $object, string $propertyName): mixed;

The abstract class AbstractUuidAwareObjectTypeConverter which implements the function defines the correct return type but does not return anything.

public function setParentObjectAndProperty(AbstractEntity $object, string $propertyName): mixed

Since a setter normally don't have to return anything, the return type should be changed to void, or if a return value is required, the method should return the correct value.

4allportaleabdullah added a commit that referenced this issue Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant