5.1 KiB
5.1 KiB
Changelog
All notable changes to this project will be documented in this file, in reverse chronological order by release.
2.8.0 - 2017-04-02
Added
- #27 adds a documentation
chapter demonstrating wrapping a PSR-7 client to use with
Zend\Feed\Reader
. - #22 adds missing ExtensionManagerInterface on Writer\ExtensionPluginManager.
- #32 adds missing ExtensionManagerInterface on Reader\ExtensionPluginManager.
Deprecated
- Nothing.
Removed
- #38 dropped php 5.5 support
Fixed
- #35 fixed "A non-numeric value encountered" in php 7.1
- #39 fixed protocol relative link absolutisation
- #40 fixed service manager v3 compatibility aliases in extension plugin managers
2.7.0 - 2016-02-11
Added
- #21 edits, revises, and prepares the documentation for publication at https://zendframework.github.io/zend-feed/
Deprecated
- Nothing.
Removed
- Nothing.
Fixed
- #20 makes the two zend-servicemanager extension manager implementations forwards compatible with version 3, and the overall code base forwards compatible with zend-stdlib v3.
2.6.0 - 2015-11-24
Added
- #13 introduces
Zend\Feed\Writer\StandaloneExtensionManager
, an implementation ofZend\Feed\Writer\ExtensionManagerInterface
that has no dependencies.Zend\Feed\Writer\ExtensionManager
now composes this by default, instead ofZend\Feed\Writer\ExtensionPluginManager
, for managing the various feed and entry extensions. If you relied onExtensionPluginManager
previously, you will need to create an instance manually and inject it into theWriter
instance. - #14 introduces:
Zend\Feed\Reader\Http\HeaderAwareClientInterface
, which extendsClientInterface
and adds an optional argument to theget()
method,array $headers = []
; this argument allows specifying request headers for the client to send.$headers
should have header names for keys, and the values should be arrays of strings/numbers representing the header values (if only a single value is necessary, it should be represented as an single value array).Zend\Feed\Reader\Http\HeaderAwareResponseInterface
, which extendsResponseInterface
and adds the methodgetHeader($name, $default = null)
. Clients may return either aResponseInterface
orHeaderAwareResponseInterface
instance.Zend\Feed\Reader\Http\Response
, which is an implementation ofHeaderAwareResponseInterface
. Its constructor accepts the status code, body, and, optionally, headers.Zend\Feed\Reader\Http\Psr7ResponseDecorator
, which is an implementation ofHeaderAwareResponseInterface
. Its constructor accepts a PSR-7 response instance, and the various methdos then proxy to those methods. This should make creating wrappers for PSR-7 HTTP clients trivial.Zend\Feed\Reader\Http\ZendHttpClientDecorator
, which decorates aZend\Http\Client
instance, implementsHeaderAwareClientInterface
, and returns aResponse
instance seeded from the zend-http response upon callingget()
. The class exposes agetDecoratedClient()
method to allow retrieval of the decorated zend-http client instance.
Deprecated
- Nothing.
Removed
- Nothing.
Fixed
- #5 fixes the enclosure length check to allow zero and integer strings.
- #2 ensures that the
routine for "absolutising" a link in
Reader\FeedSet
always generates a URI with a scheme. - #14 makes the following
changes to fix behavior around HTTP clients used within
Zend\Feed\Reader\Reader
:setHttpClient()
now ensures that the passed client is either aZend\Feed\Reader\Http\ClientInterface
orZend\Http\Client
, raising anInvalidArgumentException
if neither. If aZend\Http\Client
is passed, it is passed to the constructor ofZend\Feed\Reader\Http\ZendHttpClientDecorator
, and the decorator instance is used.getHttpClient()
now always returns aZend\Feed\Reader\Http\ClientInterface
instance. If no instance is currently registered, it lazy loads aZendHttpClientDecorator
instance.import()
was updated to consume aClientInterface
instance; when caches are in play, it checks the client againstHeaderAwareClientInterface
to determine if it can check for HTTP caching headers, and, if so, to retrieve them.findFeedLinks()
was updated to consume aClientInterface
.