We are pleased to announce the immediate availability of Apigility 1.0.0beta3!
This is our third -- and likely last! -- beta release of Apigility! The features in this release are mainly around stabilization.
Most of the work we've performed since beta2 was on zf-deploy, our packaging/deployment tool. We made the following changes:
self-updatecommand; this will check https://packages.zendframework.com/ for any new versions, and, if found, do an "in-place" update of the tool. (Note: the library we use that provides this functionality often emits PHP fatal errors; in practice, however, we've noticed that the process works even when such errors are reported.)
RouteMatchersubcomponent that provides more flexibility around argument handling, and are now shipping this in the module zf-console.
In addition to these architectural changes, we also implemented two new features in the tool:
deployment.xmland any scripts you will be using.
With these changes, we feel that
zf-deploy is ready for inclusion in a stable Apigility release!
We've received a number of documentation improvements since beta2, and added a few documents as well.
In addition to the deployment and console tooling, we made the following changes:
zf-api-problemto merge in any headers set in the application response object before sending the API Problem response. This ensures that any previously set headers are also set -- solving several issues observed when using third-party modules for Cross Origin Resource Sharing (CORS), as well as HTTP authentication.
zf-oauthnow both allow you to specify configuration via a
storage_settingskey; this change allows you to specify custom tables for both the PDO and Mongo adapters.
At this time, we feel Apigility has become very stable, and that we have addressed the most pressing usability issues. We anticipate issuing a stable release next week (week of 5 May 2014).
As noted in previous beta announcements, reaching stability is only the first step, however! Features such as "Doctrine-Connected", "Mongo-Connected", and "DB-Autodiscovery" REST services are already either implemented or will be soon, and we will be debuting these in a 1.1 version in the very near future.
Subscribe to this blog via RSS.