Task #55953

Repair and streamline ValueObject support

Added by Adrian Föder over 7 years ago. Updated over 6 years ago.

Status:
New
Priority:
Could have
Assignee:
-
Category:
Persistence
Target version:
-
Start date:
2012-05-21
Due date:
% Done:

50%

Estimated time:
(Total: 0.00 h)
Sprint:
PHP Version:
Has patch:
No
Complexity:

Description

This is intended to be a wrapper task for various bugs and conspicuousnesses regarding Flow's ValueObject support


Subtasks

Bug #37357: more suitable ValueObject hash creation for DateTime casesResolvedAdrian Föder2012-05-21

Actions
Bug #51236: ValueObject Identity generation broken in some casesResolvedPhilipp Maier2013-08-21

Actions
Bug #55954: Associations to ValueObjects should not be cascade all'dNew2014-02-13

Actions
Feature #51405: Fix OneTo* associations from ValueObjectsRejectedAdrian Föder2013-08-27

Actions
Bug #54046: Removal of ValueObjects from a ManyToMany relationship is not possibleNew2013-11-28

Actions
Feature #59672: Add support for Doctrine 2.5 embeddablesUnder ReviewAlexander Berl2014-06-19

Actions
#1

Updated by Alexander Berl over 7 years ago

  • Estimated time set to 0.00 h

Doctrine 2.5 will finally support ValueObjects in the form of @Embedded/@Embeddable:
https://github.com/doctrine/doctrine2/pull/835
https://github.com/schmittjoh/doctrine2/commit/9ad376c0064fae0c8ae6f6c3e15406936323727c

However, it still does not feature collections of ValueObjects in that manner:
http://www.doctrine-project.org/jira/browse/DDC-2826

Also ValueObjects containing ValueObjects is not currently possible.

Still, this is a huge step forward in regards to properly designing Domain Models, so should be supported in Flow.
I suggest providing some way of annotating ValueObject to behave as is (quasi entity object) or as embeddable.

#2

Updated by Alexander Berl over 7 years ago

  • Estimated time deleted (0.00 h)
#3

Updated by Bastian Waidelich over 6 years ago

  • translation missing: en.field_remaining_hours deleted (0.0)

It would be great if we could tackle this for Flow 3.0 (feature freeze in 2 weeks). I'll happily help reviewing and testing!
Can we maybe move the remaining open issues to jira.typo3.org?

Also available in: Atom PDF