Download the PHP package ryancco/laravel-uuid-models without Composer
On this page you can find all versions of the php package ryancco/laravel-uuid-models. 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 laravel-uuid-models
Laravel UUID Models
This package provides a simple trait to be used on Laravel Eloquent Models to provide a drop-in solution for UUID route keys (rather than auto-incrementing ID's).
Installation
The only supported automated installation is via Composer
Usage
Once the package has been installed, you can add the trait to any Eloquent Models you wish to have UUID route keys.
Next, add a column to these model's database tables to store the UUID; here's an example migration:
Now you can use the configured UUID attribute as a route key just as you would with an auto-incrementing ID route key.
Routes
Tests
Configuration
By default, the route key is named 'uuid', but this can be configured to whatever you would like.
Caveats
One thing to take note of, is that the UUID generation is triggered when the model event "creating" is triggered. The most important thing to keep in mind, and why this is the case, is that the UUID will not be generated when instantiating a model via the new keyword* but rather once it has been persisted to (or retrieved from) the database.
If the situation arises where you need the UUID generated before the "creating" model event is fired, you can manually call the following method:
All routes will work assuming they're generated with the route() helper.
Contributing
Please report any problems by creating an issue and pull request (encouraged, but not required).
