Download the PHP package illuminatech/model-route without Composer
On this page you can find all versions of the php package illuminatech/model-route. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 model-route
Real Laravel Model Route Matching
This extension allows continuing route matching in case bound model does not exist.
For license information check the LICENSE-file.
Installation
The preferred way to install this extension is through composer.
Either run
or add
to the require section of your composer.json.
Usage
This extension allows continuing route matching in case bound model does not exist.
Imagine we need to create URL structure like the one GitHub has. There are individual users and organizations, each of which has its own page responding the URL starting from their name:
- https://github.com/klimov-paul - user's page, where "klimov-paul" - name of the user.
- https://github.com/illuminatech - organization's page, where "illuminatech" - name of the organization.
Most likely, in your project users and organizations will be stored in different database tables, so the Laravel routes configuration for this case will look like following:
And the controllers code will look like following:
However, this does not work correctly. The problem is the second route ("organizations.show") will never be matched as any organization name will be compared against first route ("users.show") only, triggering 404 error on attempt to access organization's page.
This extension solves this problem via extra URL matching validator - \Illuminatech\ModelRoute\ModelRouteValidator.
Being registered, it adds particular model existence as a matching condition for the routes. This allows to pass matching
to the next route, in case model, bound to the current one, does not exist. The best place to register this validator will
be your route service provider. For example:
Once it is set, the routes specified above will be parsed correctly. In case there is no User record matching the requested URL route 'users.show' will be considered as 'not matched' and routing will continue to 'organizations.show'.
\Illuminatech\ModelRoute\ModelRouteValidator allows setup of the route parameter binding in the similar way to the standard explicit binding.
Binders are set via \Illuminatech\ModelRoute\ModelRouteValidator::setBinders() as an array, which key is the route parameter name
and value is a binder specification. Each binder can be specified as:
-
string, Eloquent model class name, for example: 'App\Models\User'; in this case parameter binding will be searched in this class using a its route key field.
-
string, pair of Eloquent model class name and search field separated by
@symbol, for example: 'App\Models\Item@slug'; in this case parameter binding will be searched in the specified model using specified field. - callable, a PHP callback, which should accept parameter raw value and return binding for it; in case no binding is found -
nullshould be returned.
For example:
Note: do not specify standard explicit route parameter binding for the parameter covered by
\Illuminatech\ModelRoute\ModelRouteValidator::setBinders(), as it will cause extra redundant database query. Parameter binding will be setup by\Illuminatech\ModelRoute\ModelRouteValidatorautomatically.
Performance Tuning
Remember that you should specify routes for any static pages before you write the route with model binding. While this extension allows routes matching to continue, if binding does not exist, matching check comes with the cost of a database query. Thus in our 'GitHub' example routes to any predefined site sections like static pages, contact page or blog, should be described beforehand:
Unfortunally, you can not always control the order of all your routes definition. Some packages like Telescope,
Horizon and Nova register their own routes via separated service provider.
Those routes may appear to be registered after our "users.show" and "organizations.show" ones.
You may manually exclude particular URL paths from the matching using \Illuminatech\ModelRoute\ModelRouteValidator::setIgnoredUrlPaths().
For example:
With such configuration parsing of the URLs starting from '/telescope', '/horizon' or '/nova' will never trigger a database query around "users.show" and "organizations.show" routes.
