You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
I know it may be a bit too complicated due as part of migration to zf3. It makes sense to change static zend-feed interface to dynamic.
class Reader
{
public function __construct(HttpClient $http = null, CacheAdapter $cache = null)
public function import()
{
$cache = $this->getCache();
$client = $this->getHttpClient();
$cacheId = 'Zend_Feed_Reader_' . md5($uri);
...
}
}
It will break back comparability with version 2.*. But It's necessary changes if we want to have clear, easy management code that can be used in any application without global static variables.
The text was updated successfully, but these errors were encountered:
Having done the work to separate the plugin manager and http dependencies, I can attest to the difficulties in testing the compliment currently; static usage makes this quite cumbersome!
If we're going to break BC anyway, I'd argue we should also target PSR-6 interfaces (particularly since with is being done to provide psr-6 compatibility in zend-cache). That particular change would affect also the pubsdubhubbub subcomponent, but not the writer.
Also it will be great to migrate "writter" because it uses the same weird static plugin manager functionality
/**
* @var ExtensionManagerInterface
*/
protected static $extensionManager = null;
I know it may be a bit too complicated due as part of migration to zf3. It makes sense to change static zend-feed interface to dynamic.
It will break back comparability with version 2.*. But It's necessary changes if we want to have clear, easy management code that can be used in any application without global static variables.
The text was updated successfully, but these errors were encountered: