This package is abandoned and no longer maintained. The author suggests using the sprocketbox/laravel-toolkit package instead.

v3.3.1 2018-03-28 16:37 UTC

This package is auto-updated.

Last update: 2020-01-09 10:54:57 UTC


Latest Stable Version Total Downloads Latest Unstable Version License

This toolkit aims to simplify the day to day development of Laravel applications. It has some basic functionality and modifications that I find myself using in almost every project.


Version PHP Laravel
v1 >= 5.6.4 5.3
v2 >= 5.6.4 5.4
< v3.2 >= 7.1 5.4
=> v3.2 >= 7.1 5.5+


Package is available on Packagist, you can install it using Composer.

composer require ollieread/laravel-toolkit


There are four pieces of functionality offered by this toolkit.


This toolkit provides two different scopes, packaged up. Please note, these only provided additional functionality to aid you, you have to handle the database schema side yourself.


If you have a model that has an enabled/active state, you can add this functionality by using the following contract and trait.


Adding these to your model will automatically add the following scope.


Your enable state column must be a boolean/int field. If it is called anything but enabled you can override the property provided by the trait.

protected $enabled = 'enabled';

Once all of this has been added, querying this model will only return the enabled entries by default. To return all, use the following method, much like soft deletes.


If you only want disabled, use the following.



If you have a model that is orderable, you can add this functionality by adding the following trait and contract to your model.


This will add the following global scope.


Your queries will now be ordered by the order field, the name of which is provided by overriding the property provided by the trait. This column must be an integer.

protected $order = 'order';

You can change the order of a given model by using the following self explanatory macros.


Moving a row up, down, to the top or to the bottom, will correct the order value for all other rows. The values of the column will be numeric, with the top being 0.

Base Validator

The base validator is a step away from Form Requests. This is primarily due to my dislike of having the HTTP layer validate data, which is not its job.

To create a validator, extend the following class;


Next you define your rules with the following method;

public function getRules(): array {
    return [];

You can also optionally override the following method, to provide custom messages;

public function getMessages(): array {
    return [];

To validate your data, you can do the following;

$myValidator = MyValidator::validate($arrayOfData[, $model])

The second argument allows you to pass in a model (useful when validating update forms). This model is available within the getRules() and getMessages() methods as $this->model.

A Laravel validation exception is thrown automatically should validation fail.

To return an instance of the underlying validator you can do the following;


Base Repository

The base repository is an abstract class that I have all of my repositories extend. This repository by default is designed to work with Eloquent.

To create a repository, extend the following class;


To set the model for your repository, add the following property;

property $model = MyModel::class;

Make (protected)

To retrieve a new instance of your model, call the following;


Query (protected)

To retrieve a new query on a new instance of your model, call the following;


This method primarily exists as helper (calls $this->make()->newQuery()) so that my IDE doesn't cry at me.

Get ID (protected)

To retrieve the id from a variable that is either the id, or an instance of the model, call the following;



This is a base deletion method, if you pass in an ID it uses a query, if you pass in a model it calls the helper. To access it, call the following;


Get One By

This a method to retrieve a single row by either a key => value, or an array of key => values, to use it, call the following;

$repository->getOneBy($key, $value)
$repository->getOneBy([$key1 => $value1, $key2 => $value2])

This method is available as a magic method, so you can do the following;


Get By

This method is the same as the above, except it will return all matched results, rather than just one. To use it, call the following;

$repository->getBy($key, $value)
$repository->getBy([$key1 => $value1, $key2 => $value2])

This method is available as a magic method, so you can do the following;


Transaction (static)

To start a transaction, call the following;

MyRepository::transaction(function () {
    return true;    

This method behaves exactly the same way as DB::transaction().


For simplicity, I like to add the method definitions to the class level phpdoc block of my repositories, like so;

 * Class MyRepository
 * @method MyModel make()
 * @method null|MyModel getOneById(int $id)
 * @package My\Repositories

User Model

To gain access to a password setting mutator (automatically hashes) and a helper method isPassword($password) to compare passwords, have your user models extend the following;


This model extends the default auth user, so you still retain that functionality.