Set routes in a 'latter overwrite' manner

[lenton]

I propose that routes be set in a 'later routes overwrite' manner instead of the current 'first come, first serve'.

It's a problem for two reasons:

• It's not logically intuitive to programmers, we are used to later defined things overwriting.
• It forces modules to be loaded in the wrong (reverse) order.

When modules can be loaded in the correct order, later initialisation files (such as in application) can manipulate objects created by previous initialisation files.

[enov]

maybe separate Routes into routes.php and have them loaded top to bottom?

[lenton]

@enov That would still mean you can't interact with routes which have been set in a lower module and it would break all existing modules which use routes.

[enov]

You mean we can't interact with routes from init.php?

[lenton]

Nope, from a route.php which is in a higher module.

I think it's best to fix this one at the source of the problem.

[acoulton]

Just to be clear, are you proposing that as well as making Route::set overwrite a previously defined route with the same name, we also reverse the sequence of calling each module's init.php?