We are pleased to announce the immediate availability of Apigility 1.0.2!
This is our second maintenance release of Apigility, fixing a number of issues, and providing significant improvements for file upload capabilities.
Uploads were possible before this release, but were difficult to properly enable. Additionally, PATCH and PUT requests required manually handling the file uploads, as PHP does not natively support file uploads for those request methods; the Zend Framework 2 InputFilter component, because it utilizes PHP's native support for validating that an upload completed and for moving an upload file to a new location, also could not deal with these methods.
This release makes the following changes in order to facilitate file uploads via your Apigility API:
File uploads are only done using the
multipart/form-data media type. You will need to add that media type to the content negotiation whitelist if you plan to perform file uploads.
If you have further questions, you can consult the documentation.
While upload support is the major feature of this release, we fixed many other issues.
composer.jsonfiles that properly define the two branch aliases for the
README.mdfiles that provide a "Requirements" section linking to the
201as a potential status.
ZF\Hal\Entityinstance, and thus causing listeners on
renderEntityet. al. to receive data that could never be matched.
Many thanks for all the great issue reports and discussions on the mailing list and the various issue trackers!
We will do additional maintenance releases on an as-needed basis. The next feature release, 1.1, is in development, and includes:
We would appreciate any feedback you can provide, either in the mailing lists, in issues, or via comments on associated pull requests.
Subscribe to this blog via RSS.