[Flow] Documentation distraction

[Martin Keck]

Hi all,

one thing in the Flow getting started guide distracts me always whenever I come across it. On [1] it says: 
"The concept of aggregates simplifies the overall model because all objects of an aggregate can be seen as a whole: on deleting a post, the framework also deletes all associated comments and tags because it knows that no direct references from outside the aggregate boundary may exist."

I agree in principal. But actually I would not expect tags to be deleted when I delete a Blog post they are attached to, as I'd say that in a real life scenario posts and tags would have a manytomany relation. Maybe it's nitpicking, but I don't find this example very well chosen and a little bit misleading, especially for beginners. 
In addition I would even say, that the tags should have a repository. Ok, one could argue they are value objects and seem to be placed intentionally in the aggregate by the example author to make his point clear. But think about a simple tag list in the blog. I'd find it a little bit strange, if I had to build something like that via a detour to the postRepository. A simple findAll from a potential tagRepository would seem a lot more logical to me.

Don't get me wrong, I know this is just an example to show the basics of Flow, and for that it surely works well. But then again and especially because it is a getting started guide, I would pledge for exchanging it with an example that is more consistent and comes closer to a real scenario.

What do you guys think?

Martin


[1] http://docs.typo3.org/flow/TYPO3FlowDocumentation/TheDefinitiveGuide/PartII/Modeling.html

Bloom ist Branchensieger im „Jahr der Werbung" 2013. In der Kategorie
„Alkoholische Getränke“ (B2C) landete Bloom auf dem ersten Platz. Alle Infos
auf http://www.bloomproject.de/arbeiten/show/lederer-markenpositionierung/