Christian Müller
Christian Müller
I have strong reservations about this, as it makes hiding childnodes suddenly a valid concept that we would have to carry into the future. My (personal) understanding is that childNodes...
I no longer oppose this, a discussion has been had and I find the reasoning good, and can see the benefit of having this option.
This is probably related to https://github.com/neos/neos-development-collection/issues/1280
Note, I had to make this a breaking change and fix the loaderUri as the linkEditor NEEDS the loaderUri to work because it operates on assets and nodes and needs...
Yeah, tricky issue, the collation really only drives query behavior, so indeed the query will happen case insensitive, the stored data should still be correctly cased though as the collation...
Ok, just for clarification > backwards compatibility we dispatcch the "Neos\Flow\Mvc\Dispatcher", "afterControllerInvocation" event AFTER a cli request was handled This happened before the change as well, we just continue doing...
Why would it be expected? I don't even know why it should be possible in the first place? This is an application specific syntax expression (aka path syntax) why does...
`./flow configuration:show --type NodeTypes --path "Vendor.Site:My.NodeType"` should do fine?
Note: No it doesn't, got it now!
Shouldn't we then rather think about a nice syntax extension for the scope? Eg. `[Vendor.Site:My.NodeType].properties` Obviously we need to select the separate well! The brackets look nice but _might_ collide...