This package is in development at the moment. I will expand the documentation soon!

composer require donny5300/modulair-router dev-master

Add the ServiceProvider

Donny5300\ModulairRouter\ServiceProvider::class,

Add the router singleton to /project/path/bootstrap/app.php

$app->singleton('router', Donny5300\ModulairRouter\Router::class);

Add the dynamic resource bindings to your routes.php

$router->dynamicResourceBindings();

Configuration can be done by publishing the configuration file.

You should use Artisan to copy the default configuration file to /config/modulair-router.php with the following command:

php artisan vendor:publish --provider="Donny5300\ModulairRouter\ServiceProvider"

Add the exceptions to your Exceptions/Handler.php

if( $e instanceof ControllerNotFoundException )
{
	return app( ControllerNotFoundExceptionController::class )->missingController( $e );
}

if( $e instanceof ActionNotFoundException )
{
	return app( ActionNotFoundExceptionController::class )->missingAction( $e );
}

if( $e instanceof ViewNotFoundException )
{
	return app( ViewNotFoundExceptionController::class )->missingView( $e );
}

if( $e instanceof DatabaseRouteNotFoundException )
{
	return app( RouteException::class )->missingRoute( $e );
}

To change the location of your custom views for example; the /system/namespaces/, change the system_views in your config. The user key will now direct to user.management.(methodName)

For easy development, I've added some exceptions:

• ViewNotFound
• ActionNotFound
• ControllerNotFound
• DatabaseRouteNotFound

When a view is not found, you will be redirected to the ViewNotFoundController, where you can create a view with just one click. The path will always be: namespace/module/controller/action

Just throws a exception to notify you that the method is not found in the ClassController

A exception that notifies you about the missing controller. There can be two scenarios here: The file doesn't exist or you have made a typo in the namespace/class name. Both will be answered by the view.

To make sure that all namespaces, modules, controllers and actions are registered, a exception will be thrown when one of those aren't available. You will be redirected to the RouteException (controller) (need to rename it) and there will be a proposal for you.

It can be annoying to do the same thing twice when creating a application. This method gives you the opportunity to sync one environment with another. Enter the URL with the routes that are available (by default /system/modulair-routes) and the system will display all missing or deleted routes. Select which items you wish to restore and voila, youre done.

Notice: you can set a default sync link in your modulair-router.php config

All namespaces, modules, controllers and actions, can be stored once. They will be removed with soft delete and when you sync with another environment that has the item, it will be restored. But sometimes you want to make a fresh start and remove all the soft deletes. Or just restore all of it. Hit the clean-up button and the packages will do the rest.

Some actions should not happen on a production environment. Such as creating a view, route creation or a ControllerClass. Set the debug in your config to false, to prevent actions that can harm your application. When debug is false, a DeveloperMode exception will be thrown.

For any questions: please create an issue and label it as _question. Thank you!