How are you organizing your factories as your project gets larger?

[exts]

Seems like there's a growing amount of factory classes as my project gets larger with more actions and middleware there's a paired factory to inject the dependencies I need for each and it seems just a bit unorganized by just throwing the factory class in the same folder.

Maybe it's just a weird feeling since this is the first time I've done single action classes instead of controllers which paired all these actions in one file and I'd only have to deal w/ one file to inject the dependencies rather than say 8 for a basic CRUD (pairing each one w/ factories for injecting for examples.

Is it just something I need to get used to, or is there a way to organize all these factory files?

[froschdesign]

With zend-servicemanager you have some options to reduce the number of factory classes:

• Abstract factories
• Config Abstract Factory
• Reflection Factory

Look also at this tutorial from Matthew Setter: "How To Do RAD Prototyping and Development With The ReflectionBasedAbstractFactory"

[exts]

Thanks for the resources :).I also just learned that middleware sent through the pipe doesn't require factories which is nice. actually that's false, I misread that last bit

[froschdesign]

Btw. please add your further questions to the new Zend Framework Forum, because this is a bug tracker and not a support forum. Thanks!

[exts]

@froschdesign that expressive link doesn't exist, don't think there are individual forums yet or it's not public to guest users?

[froschdesign]

@exts Mmmh, Login should help.

[froschdesign]

ping @weierophinney

[exts]

@froschdesign works now

[kynx]

Not for me :(

Error while trying to load Something went wrong.

[exts]

@kynx make sure you're logged in

[froschdesign]

@kynx Problem fixed! See: zendframework/zf3-web#68