[FLOW3-general] How does routes work with new vendor prefix?

[Robert Lemke]

Hi Julle,

Am 04.08.2011 um 17:18 schrieb Christian Jul Jensen:

> after upgrading recently the routes to my app couldn't resolved. It's just the default FLOW3 routing, no special setup.
> 
> After some debugging I realized that I had to call
> "webroot/Vendor.Package/Controller" instead of just
> "webroot/Package/Controller".
> 
> This makes sense of course, but I was wondering if this is the way the default routes is intended to work now, and you'll have to define custom routes for simpler syntax?


This is how it currently works - the schema packagekey/controllername/actionname is still the same.

But certainly, the URLs don't look that nice anymore, so the question is if we can / should implement a default behavior which would, for example, allow to access \RobertLemke\Nothing\FooController->barAction() with:

   http://myflow3host/robertlemke/nothing/foo/bar.html

Might be possible, but is not implemented yet. I guess we can add that feature in beta 2 if we want, because it wouldn't be a breaking change and is rather cosmetic than necessary.

Cheers,
Robert