Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/kennedy-osaze/laravel-api-response
Renders consistent HTTP JSON responses for API-based projects
https://github.com/kennedy-osaze/laravel-api-response
api json laravel php-8 response
Last synced: about 2 hours ago
JSON representation
Renders consistent HTTP JSON responses for API-based projects
- Host: GitHub
- URL: https://github.com/kennedy-osaze/laravel-api-response
- Owner: kennedy-osaze
- License: mit
- Created: 2022-04-22T01:29:36.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2023-07-03T16:03:09.000Z (about 1 year ago)
- Last Synced: 2024-09-24T20:05:39.429Z (about 4 hours ago)
- Topics: api, json, laravel, php-8, response
- Language: PHP
- Homepage:
- Size: 61.5 KB
- Stars: 65
- Watchers: 2
- Forks: 8
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE.md
Awesome Lists containing this project
README
[](https://github.com/kennedy-osaze/laravel-api-response/actions?query=workflow%3ACI+branch%3Amain)
[](https://packagist.org/packages/kennedy-osaze/laravel-api-response)
[](LICENSE.md)
[](https://packagist.org/packages/kennedy-osaze/laravel-api-response)
****
Laravel API Response is a package that helps to provide and render a consistent HTTP JSON responses to API calls as well as converting and formatting exceptions to JSON responses.
## Version Compatibility
Laravel | Laravel API Response
:---------|:----------------------
9.x | 1.x
10.x | 2.x
## Installation
You can install the package via composer:
```bash
composer require kennedy-osaze/laravel-api-response
```
You can publish the translation files using:
```bash
php artisan vendor:publish --tag="api-response-translations"
```
This will create a vendor folder (if it doesn't exists) in the `lang` folder of your project and inside, a `api-response/en` folder that has two files: `errors.php` and `success.php`. Both files are used for the translation of message strings in the JSON response sent out.
Optionally, you can publish the config file using:
```bash
php artisan vendor:publish --tag="api-response-config"
```
## Usage
### Using Package Traits
This package provides two traits that can be imported into your projects; namely:
- The `\KennedyOsaze\LaravelApiResponse\Concerns\RendersApiResponse` trait which can be imported into your (base) controller class, middleware class or even your exception handler class
- The `\KennedyOsaze\LaravelApiResponse\Concerns\ConvertsExceptionToApiResponse` trait which should only be imported into your exception handler class.
So we can have on the base controller class (from which all other controller may extend from):
```php
okResponse('This is a random message', $data = null, $headers = []);
return $this->createdResponse('This is a random message', $data = null, $headers = []);
return $this->acceptedResponse($message, $data, $headers);
return $this->noContentResponse();
return $this->successResponse($message, $data = null, $status = 200, $headers = []);
// Successful Responses for \Illuminate\Http\Resources\Json\JsonResource
return $this->resourceResponse($jsonResource, $message, $status = 200, $headers = []);
return $this->resourceCollectionResponse($resourceCollection, $message, $wrap = true, $status = 200, $headers = []);
// Error Responses
return $this->unauthenticatedResponse('Unauthenticated message');
return $this->badRequestResponse('Bad request error message', $error = null);
return $this->forbiddenResponse($message);
return $this->notFoundResponse($message);
return $this->clientErrorResponse($message, $status = 400, $error = null, $headers = []);
return $this->serverErrorResponse($message);
return $this->validationFailedResponse($validator, $request = null, $message = null);
$messages = ['name' => 'Name is not valid'];
$this->throwValidationExceptionWhen($condition, $messages);
```
Also to handle exceptions, converting them to API response by using the `\KennedyOsaze\LaravelApiResponse\Concerns\ConvertsExceptionToApiResponse` trait in your exception handler which provides the `renderApiResponse` public method and this can be used as follows:
```php
renderApiResponse($e, $request);
}
}
```
You could also use the `renderable` method of the handler class:
```php
renderable(function (Throwable $e, $request) {
return $this->renderApiResponse($e, $request);
});
}
}
```
### Using Package Classes
At the core of the above methods, there is an underlying `ApiResponse` class being called that can also be used as follows:
```php
use KennedyOsaze\LaravelApiResponse\ApiResponse;
$response = new ApiResponse($status = 200, $message = 'Hello world', $data = ['age' => 20], $header = []);
return $response->make();
// Result
{
"success": true,
"message": "Hello world",
"data": {
'age' => 20
}
}
// OR
return ApiResponse::create(400, 'Error occurred');
// Result
{
"success": false,
"message": "Error occurred"
}
// We could also have
$validator = Validator::make([], ['name' => 'required']);
return ApiResponse::fromFailedValidation($validator);
// Result
{
"success": true,
"message": "Validation Failed.",
"errors": [
"name": {
"message": "The name field is required",
"rejected_value": null
}
]
}
// Also
$response = response()->json(['hello' => 'world']);
return ApiResponse::fromJsonResponse($response, $message = 'Hello');
// Result
{
"success": true,
"message": "hello"
"data": {
"hello": "world"
}
}
```
If you would like to change the format for validation errors, you may call the `registerValidationErrorFormatter` static method of the `ApiResponse` class in the boot method of your `App\Providers\AppServiceProvider` class or any other service provider you want. You can do something like this:
```php
$validator->errors()->all(),
];
});
}
```
### Response Data
The response data `$data` to be rendered for successful response can be any of the following type:
- array e.g. `['name' => 'Dummy']`
- standard object e.g. `new stdClass`
- integer e.g. `1`
- boolean e.g. `true`
- any Model object, `instance of \Illuminate\Database\Eloquent\Model`
- any Collection object, `instance of \Illuminate\Support\Collection`
- any JsonResource object, `instance of \Illuminate\Http\Resources\Json\JsonResource`
- any Jsonable object, `instance of \Illuminate\Contracts\Support\Jsonable`
- any JsonSerializable object, `instance of \JsonSerializable`
- any Arrayable object, `instance of \Illuminate\Contracts\Support\Arrayable`
Any of the above can be used stored as `$data` and used thus:
```php
use \KennedyOsaze\LaravelApiResponse\ApiResponse;
ApiResponse::create(200, 'A message', $data)
```
For API Resources [JsonResources](https://laravel.com/docs/9.x/eloquent-resources "JsonResources") , you can create JSON responses by doing the following:
```php
use App\Models\Book;
use App\Http\Resources\BookResource;
use App\Http\Resources\BookCollection;
use KennedyOsaze\LaravelApiResponse\ApiResponse;
$resource = new BookResource(Book::find(1));
return ApiResponse::fromJsonResponse($resource->response(), 'A book');
// Also
$collection = BookResource::collection(Book::all());
return ApiResponse:::fromJsonResponse($collection->response(), 'List of books');
// Also
$collection = new BookCollection(Book::paginate());
return ApiResponse::fromJsonResponse($collection->response, 'Paginated list of books')
```
### Response Messages
This package uses translation files to translate messages defined when creating responses. This packages, as described earlier, comes with two translation files: `success.php` and `errors.php`. The `success.php` contains translations for success response messages while `errors.php` contains that of error response messages.
Given that you have a `success.php` translation file as thus:
```php
'User account created successfully',
'invoice_paid' => 'Invoice with number :invoice_number has been paid.',
];
```
The `ApiResponse` class would be able to translate messages as follows:
```php
['invoice_number' => 'INV_12345']
]);
// Result
{
"success": true,
"message": "Invoice with number INV_12345 has been paid."
}
// Also:
return ApiResponse::create(200, 'invoice_paid', [
'_attributes' => ['invoice_number' => 'INV_12345'],
'name' => 'Invoice for Mr Bean',
'amount' => 1000,
'number' => 'INV_12345'
]);
// Result
{
"success": true,
"message": "Invoice with number INV_12345 has been paid.",
"data": {
"name": "Invoice for Mr Bean",
"amount": 1000,
"number": "INV_12345"
}
}
```
This is similar to how messages for error responses are translated except with the fact that the error messages are read from the `errors.php` translation file instead (or whatever you specify in the config file).
Also, for error messages, you can decide that error response should have error codes. You can provide error codes in your responses in a couple of ways:
```php
'request_failed' // The error code here is "request_failed"
]);
// Result
{
"success": false,
"message": "Error message comes here.",
"error_code": "request_failed"
}
```
Also, you can use the `errors.php` translation file to translate error codes. Given the below `errors.php` file:
```php
return [
'error_code' => [
'example_code' => 'Just a failed error message',
'error_code_name' => 'Example error message with status :status',
],
];
```
We can have a response with error code as follows:
```php
['status' => 'FAILED']
]);
// OR
return ApiResponse::create(400, 'error_code.error_code_name:status=FAILED');
// Result
{
"success": false,
"message": "Example error message with status FAILED",
"error_code": "error_code_name"
}
```
## Testing
```bash
composer test
```
## Changelog
Please see [CHANGELOG](CHANGELOG.md) for more information on what has changed recently.
## Contributing
Please see [CONTRIBUTING](CONTRIBUTING.md) for details.
## Security Vulnerabilities
If you discover any security related issues, please email [[email protected]](mailto:[email protected]) instead of using the issue tracker.
## Credits
- [Kennedy Osaze](https://github.com/kennedy-osaze)
- [All Contributors](../../contributors)
## License
The MIT License (MIT). Please see [License File](LICENSE.md) for more information.