Download the PHP package wendelladriel/larapi without Composer

LARAPI

Opinionated API Skeleton created with Laravel

Configuring the project

This will:

• Create the project
• Install the dependenciesr
• Copy the .env.example to .env in the project root;
• Generate the APP_KEY
• Generate the JWT_SECRET
• Configures the Git Hooks for the project;

Update your .env file as needed;

Run the migrations and the seeders:

Configure your local Virtual Host. After that visit the host URL and you will see a JSON response like below:

App Architecture

Inside the app folder will live only other folders, no files are allowed in the root. The basic architecture is composed by four main folders:

Core: The basic architecture files only are placed here:

• Exception Handler and Custom Exceptions;
• Kernel files;
• Providers;
• Middlewares;
• Base files like BaseController and BaseRepository;

Models: All the application Model classes are placed here, but no classes are allowed in the root of the directory. All models should be put into a namespace depending on its purpose, besides that there are two other folders:

• Traits for model specific Traits;
• Relations for custom relationship classes;

Repositories: All the application Repository classes are placed here, but no classes are allowed in the root of the directory. All repositories should be put into a namespace depending on its purpose, besides that, there is a Traits folder for repository specific Traits. If you create a Repository for a specific Model class, use the same namespace you gave to the Model class, per example the Models\Auth\User repository MUST be Repositories\Auth\UserRepository. ALWAYS put the suffix Repository. All repositories MUST extend LarAPI\Core\Repositories\BaseRepository

Modules: All modules of the application are placed here, per example Auth Module. No classes are allowed in the root of the directory.

Common Module: This is a Module Folder (all module folders MUST HAVE the same folder and file structure). This module was created to have ONLY common and general purpose classes:

• Commands: Command files for this module;
• Controllers: Controller files for this module. DON'T use the name in the plural form and ALWAYS put the suffix Controller. Example: UserController, ProductController. All controllers MUST extend LarAPI\Core\Http\BaseController;
• Events: Event files for this module. Try to use verbs for the name and ALWAYS put the suffix Event. Example: ActivateUserEvent;
• Listeners: Listener files for this module. Try to use nouns for the name and ALWAYS put the suffix Listener. Example: for the ActivateUserEvent use UserActivatedListener;
• Requests: Custom request files for this module.Try to use verbs for the name and ALWAYS put the suffix Request. Example: ActivateUserRequest. All requests MUST extend LarAPI\Core\Http\BaseRequest;
• Responses: Custom response files for this module. Try to use nouns for the name and ALWAYS put the suffix Response. Example: UserActivatedResponse;
• Routing: Route files for this module. Each file is a version of the API. Follow the format: v1.php, v2.php, etc;
• Services: Service files for this module. ALWAYS put the suffix Service;
• Support: Helper files for this module;
• Traits: Trait files for this module;

When you create a new Module in the app/Modules folder, add the module name to the config/modules.php file. This configuration file is also used to enable and disable modules in your API. The modules listed there will be the enabled ones.

Creating Scheduled Commands

All commands that will be scheduled on Console/Kernel MUST extends from LarAPI\Core\Console\ApiTaskCommand;

When scheduling the commands, all commands MUST be scheduled with the ->runInBackground(); method;

Features

API Documentation

LarAPI provides API documentation for your API using Swagger. You can check the API docs accessing: HOST_URL/swagger.

Auth

LarAPI provides you JWT Authentication, User Settings and User Roles out-of-the-box. You can check the default authentication endpoints on the Swagger Docs of the API.

Controllers

The LarAPI\Core\Http\BaseController class provides three helper methods for returning data from the API:

• apiSimpleSuccessResponse(int $code = Response::HTTP_CREATED): JsonResponse

• apiSuccessResponse($data, int $code = Response::HTTP_OK): JsonResponse

• apiErrorResponse(string $message, Throwable $exception = null, $code = Response::HTTP_INTERNAL_SERVER_ERROR): JsonResponse

DTOs

LarAPI provides you two generic DTOs classes that can be useful for requests of datatables.Check out LarAPI\Modules\Common\Support\DTOs\CommonTableDTO and LarAPI\Modules\Common\Support\DTOs\DateRangeDTO

Exceptions

LarAPI provides a configured Exception Handler that will return only JSON responses and also a base interface for you to identify your custom exceptions that will be handled by the custom exception handler provided. It also provides a custom exception example.

Formatter

The LarAPI\Modules\Common\Support\Formatter class provides a lot of functions to format data and helper constants to use within your code.

Git Hooks

The project has some Git Hooks to update the API documentation using Swagger, to lint the PHP code using PHP-CS-FIXER and to run the tests using PHPUnit.

Health-Check Route

LarAPI provides a health-check route if you need to check if your API is up.

Module Management

You can use the following command to create a new module in your API:

Using the config/modules.php file you can enable and disable modules of your API.

Requests

LarAPI provides you two generic Request classes that can be useful for requests of datatables. Check out LarAPI\Modules\Common\Requests\CommonTableRequest and LarAPI\Modules\Common\Requests\DateRangeRequest

Repositories

The LarAPI\Core\Repositories\BaseRepository class offers a lot of generic purposes util functions, so you don't need to waste time creating functions for simple queries:

Scheduled Commands Manager

LarAPI provides you a custom manager for scheduled commands that will help you to prevent overlapping runs and also will make it easier to debug your scheduled commands. Check out the classes: LarAPI\Core\Console\ApiTaskCommand, LarAPI\Models\Common\ApiTask and LarAPI\Repositories\Common\ApiTaskRepository.

Slack Integration

The LarAPI\Modules\Common\Services\SlackClient class provides you a simple way to send notifications to Slack. To enable this integration you need to provide the SLACK_NOTIFICATIONS_WEBHOOK ENV variable.

Credits

• Wendell Adriel
• All Contributors

And a special thanks to Caneco for the logo ✨