Download the PHP package guiwoda/route-binder without Composer
On this page you can find all versions of the php package guiwoda/route-binder. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download guiwoda/route-binder
More information about guiwoda/route-binder
Files in guiwoda/route-binder
Package route-binder
Short Description Laravel route binding, done right.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package route-binder
Route Binder
Laravel route binding, done right.
Laravel 4 or 5?
The master branch holds code compatible with Laravel 5. Releases for Laravel 5 start from the 3.0 tag.
For the Laravel 4 compatible release, go to the laravel4 branch.
The problem
Projects start simple: a few routes, maybe some resource controllers, and maybe some parameter binding here and there.
But soon, the routes.php file starts to pile up, spawning hundreds of lines, with complex nested groups and filters
or even (god forbid) having calls to App::make. Even more cumbersome, having to scroll all those lines searching for
that odd route name that you clearly forget because, who remembers those anyway?
This package helps you with (at least) three things:
- It makes your routes part of your Application by letting you use DI through the IoC container
- It lets you split up routes in multiple files (classes) without the need for old-fashioned
includesorrequires - As you'll be creating classes, you have an opportunity to declare some string constants and hold references to those nasty route names
The solution
This package is just two contracts, a config file and a ServiceProvider.
As usual, include the ServiceProvider in your config/app.php file like so:
Then, publish the package's configuration:
Afterwards, you'll need to create some classes that implement either the LaravelBA\RouteBinder\Routes interface, the LaravelBA\RouteBinder\Bindings interface or both.
Don't panic! You'll see it's a piece of cake:
And add them to the published config file (you find it now in config/routes.php):
And you're done! Now all your routes are nicely organized, and if things get out of hand, you can always split 'em up more!
The IoC Container
I love Laravel's Route model binding functionality. I must confess though, I don't use Eloquent, so I always go for the Route::bind() option.
But this feature, as powerful as it may be, is pretty nasty on your architecture. Having calls to the DB on the routes.php file
is awful, and going App::make(SomeRepository::class) does not look that much better either.
With this little package, your Bindings objects can depend on any Service or Repository layer of your application.
Now, you could even test those bindings by mocking the dependencies and expecting a call to whatever Repository::find() method
you use on route resolution!
This may look like waaaaaay too complicated a scenario right now, but trust me, you'll love it.
