Bastian Waidelich

..and maybe https://github.com/neos/neos-development-collection/pull/3914

Thanks for this! I agree to @mficzel's comments. Splitting this into smaller chunks would greatly enhance extensibility and readability. > good idea (WIP at my pc) but ill wait for...

It's been a while.. Is this one still in progress?

``` ${request.arguments.myQuery} vs. ${request.httpRequest.queryParams.myQuery} ``` Those are two different things and IMO we should really make that distinction clear. I think you should use the latter if you are interested...

After an issue @ahaeslich had today with lots of `ContentStreamWasForked` events without corresponding `Workspace` events (see [Slack discussion](https://neos-project.slack.com/archives/C3MCBK6S2/p1700048865216739)) this missing feature gets more critical and made me think: The `causationId`...

> it troubles me as this topic is marked critical Don't worry. This is critical for debugging the event log, but at least the last suggestion should be very easy...

> If it turns out to be too much work to introduce the complete causation/correlation handling for now, > we should at least add some property to the ForkContentStream command...

Reminder: We should also set some kind of "originalEventId" metadata to events published to other content streams in order to correlate those. This will allow us to detect "merges" rather...

> This problem also appears when unsetting paths I'm afraid this is a major regression. We stumbled upon this because some Monocle useCases didn't work as expected but this changes...

It seems like the `isInWorkspace()` matcher really doesn't make sense in its current form, so this might be turned into a bug ticket. But I wonder if we can find...