Naming factories “class”factory always a good idea?
Hi everyone,
I’m just learning about design patterns, and all code examples I’ve seen highlight their implementation with obvious examples such as “DogFactory” etc.
I’m wondering if this is usually done in practice, or if the class name should instead represent its purpose in the code, for example:
A factory class that resolves the manufacturer of an item from its properties, and returns that manufacturer’s specific implementation of IVendorThing, would I name that factory “VendorThingFactory” or something like “VendorThingResolver”?
I’m just learning about design patterns, and all code examples I’ve seen highlight their implementation with obvious examples such as “DogFactory” etc.
I’m wondering if this is usually done in practice, or if the class name should instead represent its purpose in the code, for example:
A factory class that resolves the manufacturer of an item from its properties, and returns that manufacturer’s specific implementation of IVendorThing, would I name that factory “VendorThingFactory” or something like “VendorThingResolver”?
