Martin Ficzel

This is the line https://github.com/neos/flow-development-collection/blob/master/Neos.Flow/Classes/Reflection/ReflectionService.php#L1385

I like the concept but not the tabs. They also could lead to conceptually errors as tabs lie in the inspector usually allow to fill values on multiple tabs which...

If someone is willing to do the work of moving Archeaopteryx we @sitegeist would be fine with that. Was always the plan in the long run. There are some changes...

Should be fine. I am for doing this

If we cannot do this properly we could remove the ContainerInterface from the object manager interface and create a psr 11 container instead that only implements psr11 and internally uses...

Generally I think the uriFor method should have the distinct parameters “routingArguments” and “queryParameters“. I know this can be done via -> withQuery but it could help to make the...

@bwaidelich I think it is important to make clear that there are routingParameters and that you can also have queryParameters at the same time. Both routingParameters and queryParameter should be...

> But maybe it's just a naming issue. I wasn't 100% happy with the name "Action" anyways Agree, if it is called "Action" i would expect it to separate routingArguments...

One thing i am not totally sure about is how this would affect uriBuilding in Fluid/Fusion especially when subrequests are involved as is the case inside of backend modules or...

Would prefer that ```php $actionUri = $uriFactory ->createFromActionRequest($actionRequest) ->for(Action::name('show')) ->withRoutingArguments(['id' => $entityId]) ->withQueryArguments(['foo', 'bar']); ``` We should use the term parameter or argument consistently.