Download the PHP package xurudragon/api-versioning-bundle without Composer
On this page you can find all versions of the php package xurudragon/api-versioning-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download xurudragon/api-versioning-bundle
More information about xurudragon/api-versioning-bundle
Files in xurudragon/api-versioning-bundle
Package api-versioning-bundle
Short Description Symfony APIVersioningBundle
License MIT
Homepage https://github.com/XuruDragon/ApiVersioningBundle
Informations about the package api-versioning-bundle
ApiVersioningBundle
Informations
This bundle provide you a way to handle multiple version of your api.
See Usage
section to know how ise this bundle
Installation
Step 1: Download the Bundle
Open a command console, enter your project directory and execute the following command to download the latest stable version of this bundle:
This command requires you to have Composer installed globally, as explained in the installation chapter of the Composer documentation.
Step 2: Enable the Bundle
Then, enable the bundle by adding it to the list of registered bundles
If you are on Symfony 3.*
look in the app/AppKernel.php
file of your project:
If you are on Symfony 4.*
look in the config/bundles.php
file of your project:
Step 3: Configuration
Nothing special to do here. Unless you want to change the header name sent to the api to processing versioning changes You can add theses entries into your config files :
Usage
Introduction
Your API reponse must always match the latest version of your API.
To support multiple versions, you must for each version of your API that breaks the backward compatibility:
- create a change class inheriting from the following abstract class:
XuruDragon\ApiVersioningBundle\Changes\AbstractChanges
- add an entry in the configuration file corresponding to the class created previously
we recommend to you the following structure:
- Create a folder named
ApiChanges
- Name your classes
ApiChangesXYZ
, withX
for theMajor
version,Y
for theMinor
version andZ
for thePatch
version
We assume that you know the semantic versioning system
Create the Change Class
Here is the 0.9.0 class version, which assumes that your API version is at least 0.9.1 .
You should now implement the apply and supports methods with your own logic.
supports
should return true
or false
following if this version change support the actual data returned by your latest api version.
apply
should do whatever you want to transform the actual data into an version that correspond to this api version. The returned array would be encoded in json and return to the api client that have make the request.
Example
Imagine that version 1.0.0 of your API adds an entry to the json output of one of the called services. This entry would be "location" within the following data array returned by your latest API version :
You must then delete this data entry so that the requested version 0.9.0 matches what the calling client is waiting for.
You can do that by modifying the previously created class with the following code :
Of course here it's a pretty simple example of delete One entry, the processing could be more more complicated.
Register your version changes class in the configuration
Here you are, no more configuration is required.