Skip to content
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.

Improve migration from zend-servicemanager-di #58

Open
tux-rampage opened this issue Dec 16, 2019 · 1 comment
Open

Improve migration from zend-servicemanager-di #58

tux-rampage opened this issue Dec 16, 2019 · 1 comment

Comments

@tux-rampage
Copy link
Contributor

From PR #35

ZF is aiming to allow easy migrations to new component versions whenever possible. For zend-di there is a component that integrated version 2 into zend-servicemanager.
Version 3 introduced a conflict-entry in it's composer.json, that states clearly zend-servicemanager-di is no longer needed. But it will also urge consumers to potentially upgrade many parts of their application.

To make life easier for these users, we should provide a new version for zend-servicemanager-di, that will deprecate it's own usage but allowing the user's to remove it's parts step by step.

Link to the discourse topic

This issue should keep track of this topic after migration to Laminas is complete.

@weierophinney
Copy link
Member

This repository has been closed and moved to laminas/laminas-di; a new issue has been opened at laminas/laminas-di#1.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants