This is a Laravel 5 package that creates RESTful API routes for your models and uses the command bus to execute CRUD requests.

Install the package via composer:

composer require osedea/laravel-rest:~0.2.1

First, add the eloquence service provider to your config/app.php file:

'Osedea\LaravelRest\LaravelRestServiceProvider'

All you models need to use the trait \Osedea\LaravelRest\Traits\CommandModel to provide some attributes and methods:

<?php

namespace Acme;

class SomeModel {
    use \Osedea\LaravelRest\Traits\CommandModel;
}

Then, publish the config file to your application:

`php artisan vendor:publish --provider="Osedea\LaravelRest\LaravelRestServiceProvider"`

You should now be good to go without having to change anything! Access /api/v1/users to see a list of users!

You need to specify the application namespace used in your project. The default is App, but if you changed it, you need to change it in the config:

<?php

return [
    'app_namespace' => 'SomethingElse'
];

If you models are in a custom namespace different from app_namespace, you can specify this config.

<?php

return [
    'models_namespace' => 'SomethingElse'
];

To add a resource to the default controller, you just have to add a line in the /config/api.php file:

<?php

return [
    'mapping' => [
        'users' => 'User',
    ]
];

If you want to use a different prefix, you can do so by specifying the prefix key:

<?php

return [
    'prefix' => 'api/v2'
];

If you don't specify the key prefix, it will default to api.

If you routes need to have a middleware set up, you can specify the middlewares or filters to use.

<?php

return [
    'middleware' => []
];

LaravelRest comes with a default REST controller to handle resources. This allows automatic actions on resources listing, showing, deleting and lising relations.

All lists are paginated by default. You can set a number of items per page for each Model by overriding a variable:

protected $perPage = 10;

You can also define a maximum for this value because it can be overridden in a request:

protected $perPageMax = 50;

And then in a request: /users?page=2&perPage=3

Sorting can be done on multiple columns by separating them with commas:

/users?sort=name,email

You can choose the order (desc or asc) by putting a - in front of a column name:

/users?sort=-id

If you don't need all fields when querying a list or a resource, you can specify which fields you need:

/users?fields=id,name

Use this only when you REALLY need to.

If you absolutely need nested relations, you specify them like so:

/users?embed=groups

LaravelRest has default commands for several actions:

• GET /{resource}: Osedea\LaravelRest\Commands\DefaultCommand\IndexCommand
• GET /{resource}/{id}: Osedea\LaravelRest\Commands\DefaultCommand\ShowCommand
• POST /{resource}/{id}: Osedea\LaravelRest\Commands\DefaultCommand\StoreCommand
• PUT /{resource}/{id}: Osedea\LaravelRest\Commands\DefaultCommand\UpdateCommand
• DELETE /{resource}/{id}: Osedea\LaravelRest\Commands\DefaultCommand\DeleteCommand
• GET /{resource}/{id}/{relation}: Osedea\LaravelRest\Commands\DefaultCommand\RelationIndexCommand

With these defaults, the mapping is enough for them to work. You can override them by creating a command using the correct namespace:

Example, to override the POST /users/{id} default command, create one called Osedea\LaravelRest\Commands\UserCommand\StoreCommand.

Those actions are very specific to a resource so the default commands may not fulfill your needs. If you want to use the default commands then your models need to have the $fillable property set.

To override the default behaviour you will have to create a command for all resources listed in the mapping file. The schema is this:

Osedea\LaravelRest\Commands\{mapping[resource]}Command\{action}Command

For example, to add the create command of the users resource, the command is:

Osedea\LaravelRest\Commands\UserCommand\StoreCommand

A command class needs to extend Osedea\LaravelRest\Commands\Command and implement Illuminate\Contracts\Bus\SelfHandling.