Alexander Berl

> With player.playlist.repeat(true) you shouldn't need the playlist.currentItem(0). I thought so too, but it is needed, because else the last item will be played once again before advancing to the...

```javascript const myPlaylist = [...]; player.playlist(myPlaylist); ... myPlaylist.push(myNextVideo); player.playlist(myPlaylist, -1); ``` should do the trick. The current playing item will not be changed with the `-1` parameter, but ofc this...

So, what's the status on this one?

Hi niko, thanks for the question! Though this is not specific to Neos.EventSourcing/Flow, it is a very fundamental question to any Event Sourced/Eventually Consistent system and here are some answers...

I agree that 25 reattempts seems a bit much. Not sure that's really a necessity in the given case, never came across a scenario where a commit would fail so...

@bwaidelich that were exactly my thoughts when I saw the PR and thought about it :)

Just a few notes on the use cases for EventBus middleware: - "for event/metadata enrichments" - that should happen pre commit (EventStore), else this enriched metadata is only transient -...

> The Domain folder doesn't make sense to me, as all of this is part of the domain really, even projections. And if they're not, they belong to a different...

> In my understanding the domain is everything about the business/world you're creating a solution for. The core domain is the part that the domain experts consider the fundamental and...

> Instead we could maybe tweak https://www.neos.io/community/values.html But that is rather pretty "meta" and on a social level. I was more aiming towards very specific goals to this package and...