Download the PHP package mnarbash/api-versioning-by-header-request without Composer
On this page you can find all versions of the php package mnarbash/api-versioning-by-header-request. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download mnarbash/api-versioning-by-header-request
More information about mnarbash/api-versioning-by-header-request
Files in mnarbash/api-versioning-by-header-request
Package api-versioning-by-header-request
Short Description A package for managing API versioning in Laravel using request headers
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package api-versioning-by-header-request
Laravel API Versioning By Header Request
This package provides middleware for managing API versioning in Laravel using request headers.
Features
- You Not Need To Change Your Routes Endpoints. You can use the same endpoints for all versions of your API.
-
API versioning by header request: This package allows you to version your API by adding the
API-VERSIONheader to the request. You can specify the supported API versions and the default API version in the configuration file. -
App version checking: This package includes a middleware that checks the
APP-VERSIONheader in the request against the supported app versions and the minimum supported app version specified in the configuration file. If the app version is not supported, the middleware returns an error response to update app. -
Customizable folder structure: You can specify a custom folder structure for the API versions in the configuration file. This allows you to organize your controllers and routes in a way that makes sense for your application.
- Api Versioning base on your controller classes: The package allows you to version your API by multi controller classes in your route define.
Youtube Video
Check out this video to see how to use this package in your project.
Installation
To install the package, run the following command:
Configuration
Add ServiceProvider to config/app.php in providers section:
To configure the package, publish the configuration file using the following command:
This will create a config/api-versioning.php file in your project. You can modify the following options in this file:
check_app_version_support: This option tells the package whether to check the app version support. If set totrue, the package will check the app version and return an error response if the app version is not supported.api_versioning_enabled: This option tells the package whether to enable API versioning. If set totrue, the package will check theAPI-VERSIONheader in the request and use it to determine the version of the API to be used.default_api_version: This option specifies the default API version to be used when theAPI-VERSIONheader is not present in the request.-
not_do_anything_when_version_is_not_set: This option tells the package whether to do anything when the version is not set. If set totrue, the package will not change the controller name when the version is not set. default_app_version: This option specifies the default app version to be used when theAPP-VERSIONheader is not present in the request.min_supported_app_version: This option specifies the minimum supported app version. If the app version in the request is less than this version, return an error response.update_urls: This option specifies the URLs to show update app.not_support_response_status_code: this option specifies the status code of the response when the app version is not supported.
To use the check api and redirect to new controller, apply it to a route as follows:
-Note: Add the newer controller in the first of array. We use this order to check the version and redirect to the older controller if version is not exist. Example: If you have 2 controller with version 1 and 2 and you want to redirect to version 1 if version 2 is not exist,
Full Example For Route File
Also you can get api version from anywhere in your code like this:
The package includes the CheckAppVersion middleware:
-
CheckAppVersion: This middleware checks the app version in theAPP-VERSIONrequest header. If the version is not supported, it returns an error. - to use the check app middleware, apply it to a api $middlewareGroups in app/Http/Kernel file as follows:
License
This package is licensed under the MIT license. See the LICENSE file for more information.
