-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write new tutorial documentation for moving from ConfigAbstractFactory #22
Comments
@GeeH Question: you mentioned at one point in development of #146 that you might write a tool that would create a factory/factories from Also, wondering, because if you are planning that, I'm curious if you think we should delay the 3.2.0 release until it's ready... Originally posted by @weierophinney at zendframework/zend-servicemanager#149 (comment) |
Is the current doc's page enough to explain the differences between Abstract Factories and Explicit Factories mentioned here and in #148 ? If it is enough, I think this issue was already resolved by #150 , so it should be closed. Originally posted by @renanliberato at zendframework/zend-servicemanager#149 (comment) |
I wonder if this is somehow fixed by #180 - even tho it does not create a factory based on Anyways, closing this as it is open since 2016 and there was no progress until 2023. Even tho we did not reached the 10 year mark here, I guess we can close this without stepping on anyones toes? |
It might be a good idea to demonstrate in the documentation a migration path from this abstract factory to an explicit factory. One of the frequent comments I've seen from folks about the deprecation of ServiceLocatorAware is that developers are unaware of how to write factories. Including some explicit steps here will help them when they have the question of, "I need to do something that falls outside the scope of this abstract factory, but I don't know how."
Originally posted by @GeeH at zendframework/zend-servicemanager#149
The text was updated successfully, but these errors were encountered: