Some functionalities are in conflict, for example, the ability to declare multiple controllers for a given path is the same as declaring aliases between routes. The aliasing structure is much more flexible tldhan the multiple controllers.
The authenticated option should probably be declared somewhere else. The fact that the user is logged in or not should be abstracted from the route declaration itself. As it has been pointed out to me, it would be more obvious to pass this information to the route action via the action context which is not really implemented yet.
Some functionalities are in conflict, for example, the ability to declare multiple controllers for a given path is the same as declaring aliases between routes. The aliasing structure is much more flexible tldhan the multiple controllers.
The
authenticatedoption should probably be declared somewhere else. The fact that the user is logged in or not should be abstracted from the route declaration itself. As it has been pointed out to me, it would be more obvious to pass this information to the route action via the action context which is not really implemented yet.