Task #55953

Repair and streamline ValueObject support

Added by Adrian Föder over 1 year ago. Updated 6 months ago.

Status:New Start date:2012-05-21
Priority:Could have Due date:
Assigned To:- % Done:

50%
Category:Persistence
Target version:-
Sprint: Has patch:No
PHP Version: 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öder

Bug #51236: ValueObject Identity generation broken in some casesResolvedPhilipp Maier

Bug #55954: Associations to ValueObjects should not be cascade all'dNew

Feature #51405: Fix OneTo* associations from ValueObjectsRejectedAdrian Föder

Bug #54046: Removal of ValueObjects from a ManyToMany relationship is...New

Feature #59672: Add support for Doctrine 2.5 embeddablesUnder ReviewAlexander Berl

History

#1 Updated by Alexander Berl over 1 year ago

  • Estimated time set to 0.00

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 about 1 year ago

  • Estimated time deleted (0.00)

#3 Updated by Bastian Waidelich 6 months ago

  • 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