Marc Henry Schultz

i will test the functionality locally - i cannot say too much about all that proxybuilding ^^

@robertlemke i really want to approve this since the syntax is much much much much fancier ... and cooler ^^ but i found out in my tests that this really...

so at the moment this feels sometimes buggy - just go around fx. in the neos dev collection and try to change to typed properties here and there -> you...

do i see this right that using `Laminas` is not crucial and just bewares us from manually string concatenating everything together?

I could also imagine a custom method in the flow Files utility: https://github.com/neos/flow-development-collection/blob/d559aca053fd64a3b2d8ed3e3c19942f61f3b9ee/Neos.Utility.Files/Classes/Files.php `Files::getResolvedPathForFileStreamWrapper('resource://foo.bar')`.

maybe one should introduce an additional interface for flow stream wrapper and then let the ResourceStreamWrapperHelper call the `getAbsolutePath` on these flow stream wrapper ...

Im not talking about persistent resources but only the local files from a package in the resources folder. (which are not stored externally) My problem is: i need to compare...

in slack there are many issues about trying to use `realpath()` on a package resource path (what doesnt work because realpath doesnt know about stream wrapper) ... (search for `realpath...

then its even better to abstract it away to not have the need to call `$package->getResourcesPath()` directly ... maybe we should put it on the `$resourceManager` as here lives already...

i now build this myself (for neos.fusion), making a feature out of this still makes sense - its just hard to get right. https://github.com/neos/neos-development-collection/pull/3659/files#diff-2bddda138583e813fb9494e8dd1a33a0749c9c7ad85b2764b340225299ad5ec4R132