Project Proposal: More flexible Node routing

[gerhard_boden]

Thanks for the examples, I think those three pretty much cover all the URL structure needs anyone can ever have

@bwaidelich

Aliases

The example you described is currently not possible, e.g.:

baz

where the node path is foo/bar.For this we could add a new node Property that allows for specifying an “alias” that would overrule the uriPathSegment property and would need to be looked up first.

Here’s a Gist to my custom prototype for the Alias scenario (did some testing yesterday: matching and resolving nodes work surprisingly well)

https://gist.github.com/gerhard-boden/e4a3883f6d38095744aaaed7c7f6b19e

As said before currently my route part handler just extends the standard frontend route part handler.
I don’t really know where to go from here:
On the one hand the my implementation is flaky because it heavily depends on the current structure of \TYPO3\Neos\Routing\FrontendNodeRoutePartHandler.

But if I write a completely independent route part handler I would basically rewrite many things that FrontendNodeRoutePartHandler already covers and that doesn’t feel right either.

So what is the best solution for now, until we clean up FrontendNodeRoutePartHandler and make node routing more flexible?

@bwaidelich

Of course this could lead to conflicts (e.g. if you had a node baz on the root level).

This is something that needs to be checked in the backend when saving the node. I see what I can come up with.

@dimaip

You are right, AOP is not a right way to do it at all. IMO, rather than overruling things, we should break up all of our routing logic into small blocks, and be able to produce custom behaviors from composition of those blocks.

That sounds very reasonable and would be the way to go I think. So we take apart the current FrontendNodeRoutePartHandler and divide the functionality into smaller parts so they can be replaced with custom solutions more easily. Or we even deliver some new routing options out of the box.