Laravel Simple Bases

A set of base classes to help create projects with Laravel

Summary

:computer:   Installation
:lock:   Configuration authentication with JWT
:satellite:   Creating an endpoint
:wrench:   Utilities on request
      :mag_right:   Filters
      :arrow_up_down:   Ordering
      :keycap_ten:   Pagination
:floppy_disk:   Intercept uuid for id
:paperclip:   Intercept base64 to file
:no_entry_sign:   Permission
:red_circle:   Exception
:triangular_ruler:   Helpers
      :keycap_ten:   fractal_transformer

About

This package creates an initial base and utilities for your Laravel projects with a focus on REST api.
Containing the following resources:

• Base class for authentication using JWT (package)
• Base class for models, with uuid and additional functions
• Base class for controller, with index, show, store, update, destrory functions implemented and each with interesting features (see detail below)
• Base class for service, in the same way that the controller has implemented functions and features (see detail below)
• Filters through the request using queryString
• Intercept uuid to id automatically
• Simple implementation of image upload via base64 in a simple way in any model
• Artisan commands to facilitate the creation of the structure
• Base class for validation (see details)
• Base class for the handler for Exceptions
• Among other features

Sample repository

Sample

Installation :arrow_up:

composer require fabio/laravel-simple-bases

Configuration authentication with JWT :arrow_up:

This package is dependent on the package tymondesigns/jwt-auth, but don't worry, it has already been installed together. It will only take a few implementations for you to have working token authentication.

Step 1

Then create a controller for authentication you can use the artisan command for this:

Step 2

Extend your controller to BaseAuth

Step 3

In your file routes routes/api.php, create a login route. Ex.:

Step 4

php artisan vendor:publish --provider="Tymon\JWTAuth\Providers\LaravelServiceProvider"

Step 5

Generate secret key

Step 6

In config/auth.php make the changes

Optional but recommended
Change the path for the User model.

Step 7

Optional, if using config with cache, execute:

Creating an endpoint :arrow_up:

Step 1

Create a table for your new endpoint

Step 2

The fabio-pv:generate-endpoint-class command will automatically create all necessary dependencies for the endpoint.It will only be necessary to provide a name for the class and the name of the table that the model will reference.

This command will create 5 classes in your versioned project in the v1 directory. If you need to change the versioning use the option --api-version=.

• Model
• Controller
• Service
• Validation
• Transformer

Step 3 Optional

If you want to validate the request body, you must implement its rules in App/Http/Validations/v1
This validation works using Laravel validation through the base class

Step 4

Create the return object from your endpoint using laravel-fractal which was created in App/Http/Transformers/v1

Step 5

Create your route in routes/api.php

Step 6

Test, if everything goes well you will have an endpoint working with the functions:

• GET with pagination

• GET

• POST

• PATCH

• DELETE

Ex.:

Utilities on request :arrow_up:

All endpoints that extend have filters ready to be used.
Note:
In the current version the filter only works for the model's main table.

Filters :arrow_up:

index_filter = Array index for the filter string
name_column = Name of the column to be applied the filter
name_operator = Operator to be applied to the filter
value = Value for the filter

Filter on related tables

As of version v0.3.0, the filter also works with the related tables.

Example:

• user endpoint response

Assuming that we only want user who have a car with motor_power equal to '140'. Our queryString will look like this:

Other example

Assuming we want all user who have car of car_type equal to 'Sporty'

Note The functioning of the filters depends on the following requirements:

• The name of the properties in transformer must be the same as the database tables. (This is related to usability)
• The relationships in the transformer must follow the same name as the models only separated by '_'.
  Model

Transformer

Ordering :arrow_up:

name_column = Name of the column to be applied the filter
order = asc or desc

Pagination :arrow_up:

Default is 10 per page

value = Can receive to disable a page or a number to change an amount per page

Intercept uuid for id :arrow_up:

On request where it is necessary to pass the relationship of another table is common to do by uuid but internally we need the id, to facilitate this 'transformation' this package has a config file where this transformation can be configured so that it happens automatically. Continue reading to learn more

MER for this example

Step 1

Publish configuration file

Step 2

Configure the file

How to configure ?

model::class = Model that receives the relationship
property_param = Parameter name in request
Model::class = Model where the relationship comes from
property_database = Property name in the model

Your file should look like this

Step 3

Test, if everything went well using the method post or patch and passing the relationship you should have the relationship in your database automatically

Intercept base64 to file :arrow_up:

This package provides an easy way to implement file upload via base64 on any model you want.
Note: Files are saved using Laravel Storage

Step 1

Run the command below to publish the configuration file

Step 2

Configure the file in

model::class = Model that will receive file
fantasy_property = Property name with base64 in the request save_location = Directory where the image will be saved () extension = File extension

Example

Step 3 Optional

If your config files are cached don't forget to run:

Step 4

Test.
Example Request

Note: the property you defined can receive multiple uploads for that, just pass an array

Step 5 Optional

If you want to show the files in the reply just use the model function
Implementation
In your transformer add a name for the property and use the helper
Note: The files function is present in all models that extend or

Example response

Update file

To update the file just pass a new parameter with the same name as the property you created with a '_uuid' at the end and in the original property pass the new file. Example:

Delete file

To delete the file, just pass a new parameter with the same name as the property you created with a '_uuid' at the end and in the original property pass the value null. Example:

Permission :arrow_up:

This package provides classes to deal with permissions, basically it checks if the user's role can access a given route or not. Note: In the current version it does not control whether the user is authenticated or not, it will still be necessary to implement middleware https://laravel.com/docs/7.x/middleware

Configuration

Step 1

Run the command
php artisan fabio-pv:generate-permission-class nome_da_class

Step 2

Configure the file giving access to the functions according to your system's rule

Example:

Tip: To make the code more elegant, define the role as constant in the role model Example:

Step 3

Define dependencies on the controller

Step 4

Create the relationship in the user model

Step 5

test

Dica

If your controller has more functions than the 4 index show store update destroy defaults, you can configure it manually as follows:

In your controller add this call at the beginning of the function:

Change permission logic By default, the BasePermission class tries to take the user's role as follows:

If you need to change the way to search for the role run the command below:

The command will generate the class

Implement the functions handle and message

Handle
Here you can change the way to search for the user's role, just don't forget to return role =)

message Here you can define the message for access denied exception

Exception :arrow_up:

This package has a base class to extend in . This class will make the return of errors more pleasant for those who use the api

Original

With

Usage
Just replace the class in with

Helpers :arrow_up:

fractal_transformer :arrow_up:

Returns an array of an existing transformer.
Created mainly to be used inside another transformer, with it you can standardize your returns from the api

Description

Example

Transformer implementation

Example response