This repository has been archived by the owner on Jan 8, 2020. It is now read-only.
Ensure DiAbstractServiceFactory takes lowest possible priority #5180
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm far from expert on all the intricacies of Zend\Di, but this
seemed necessary for my application.
AFAICT, the
Zend\ServiceManager\Di\DiAbstractServiceFactory
will be lazily added to the shared ServiceManager at an unpredictable
time. The default behaviour of
addAbstractFactory
puts this newabstract factory in front of abstract factories from modules, which leads
to the DiAbstractFactory trying to create things before module-defined
abstract factories get a chance.