Download the PHP package api-tools/api-version-manager without Composer
On this page you can find all versions of the php package api-tools/api-version-manager. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Table of contents
Download api-tools/api-version-manager
More information about api-tools/api-version-manager
Files in api-tools/api-version-manager
Download api-tools/api-version-manager
More information about api-tools/api-version-manager
Files in api-tools/api-version-manager
Vendor api-tools
Package api-version-manager
Short Description Simplify Laravel API versioning with ease. No more separate controllers—just flexibility, fallbacks, and version-specific components.
License MIT
Homepage https://github.com/dvmunjapara/api-version-manager
Package api-version-manager
Short Description Simplify Laravel API versioning with ease. No more separate controllers—just flexibility, fallbacks, and version-specific components.
License MIT
Homepage https://github.com/dvmunjapara/api-version-manager
FAQ
After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.
Example:
Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.
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.
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 PHP packages are not free to download and because of that hosted in private repositories.
In this case some credentials are needed to access such packages.
Please use the auth.json textarea to insert credentials, if a package is coming from a private repository.
You can look here for more information.
- 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.
Please rate this library. Is it a good library?
Informations about the package api-version-manager
Laravel API Version Manager
The Laravel API Version Manager Package streamlines the management of API endpoint versions in Laravel applications. This package empowers you to effortlessly handle API versioning, eliminating the necessity to create individual controllers for each version. Its design presents a flexible and efficient solution, enabling you to define fallback versions and effortlessly generate version-specific Requests and Resources.
Features
- Fallback Versions: Define fallback versions for your API routes, ensuring smooth transitions and maintaining backward compatibility.
- Single Controller: Eliminate the need to create separate controllers for each API version. Our package dynamically injects version-specific Request and Resource classes into your existing controller.
- Effortless Versioning: Easily manage API versions through route configuration. The package automatically handles the resolution of version-specific components, streamlining your development process.
Installation
You can install the package via Composer:
Configuration
Publish Config File
It is mandatory to publish the config file before using the package. You can publish the config file using the following command:
Mandatory Configurations:
- Define available
versionsarray in config - Define default version
versionin config
Other possible configurations are:
app_http_namespace(default:App\Http) - Generally we useApp\Httpnamespace to store all our requests & resources classes, but if you are using different namespace then you can define it here.api_prefix(default:api) - API prefix for all versioned routes.use_fallback_entity(default:true) - If you want to use fallback entity for all request & resource class then set this totrue, otherwise set it tofalse. For example, you defineSampleRequestin V1, and now you want to use same request in V2 then you can set this option totrueand it will automatically useSampleRequestfrom V1.
Available Commands
Create a new versioned request
Possible options:
--force: Overwrite the request if it already exists.
Create a new versioned resource
Possible options:
--collection: Create a resource collection instead of a single resource.--force: Overwrite the resource if it already exists.
Usage
Example of api.php file:
Example of SomeController.php file:
License
The MIT License (MIT). Please see License File for more information.
All versions of api-version-manager with dependencies
PHP Build Version
Package Version
Requires
laravel/framework Version
^8.0|^9.0|^10.0
The package api-tools/api-version-manager contains the following files
Loading the files please wait ....