Alexander Berl
Alexander Berl
Yes, exactly that @bwaidelich and good point with the object accessor syntax, that could be an issue. Not sure how to best deal with that in fact. At least for...
@sascha-egerer Yes, but the use case is really where you only want to pass a sub set of the variables, which happens quite often (at least for me). Also I...
Ok, so after thinking a bit about the `ExpressionNode`, I think this would not work easily with mixed notation, e.g. `{ a, b, c: d, e: { f, g: 'h'...
Needs a rebase and the typehint adjustments, but otherwise anything preventing this from getting merged? @mficzel Feature Freeze is on Friday - so this could still make it
Of course, a full revamp of the getting started example code would be the best solution. But the lower hanging fruit is at least not having the code in the...
Can someone do a rebase of this?
Thanks a lot for the deep analysis of the issue so far! I see how this must be related to the PR you mentioned and hence #1797. I'm not sure...
Can we just merge this as is (after fixing the builds) to keep the following functional changes to the ReflectionService away from the noise of these (useful! 👏) syntax changes?...
Someone up to do a rebase?
The bug is likely in https://github.com/neos/flow-development-collection/blob/master/Neos.Flow/Classes/Security/Authorization/Privilege/Entity/Doctrine/PropertyConditionGenerator.php#L511-L513 From a quick glance and decoding, this will generate a `IS NULL` check if the array (`$parameter`) is empty(=evaluates to empty string due to...