This content originally appeared on DEV Community and was authored by bilel salem
Hello everyone, السلام عليكم و رحمة الله و بركاته
The Factory Method is a creational design pattern that provides an interface for creating objects in a superclass but allows subclasses to alter the type of objects that will be created. It helps in dealing with the problem of creating objects without having to specify the exact class of the object that will be created. This is particularly useful in scenarios where the creation process is complex or involves multiple steps.
What Problem Does the Factory Method Solve?
Class Instantiation Issues: Directly instantiating objects using
newcan lead to code that is tightly coupled with specific classes. This makes the code difficult to maintain and extend.Complex Object Creation: When object creation involves several steps or configurations, using a constructor can be cumbersome and hard to read.
Subclasses Control: It provides a way for subclasses to decide which class to instantiate, allowing for more flexible and reusable code.
Key Concepts of the Factory Method
- Product: The interface or abstract class defining the objects that the factory method will create.
- Concrete Product: The implementation of the product interface.
- Creator: The abstract class or interface that declares the factory method.
- Concrete Creator: The class that implements the factory method to create an object of the Concrete Product class.
Real-World Example: Document Creation
Consider a scenario where we have an application that can create different types of documents such as Word Documents, PDF Documents, and Excel Sheets. The application should be able to generate these documents without knowing their specific implementation details.
Step-by-Step Implementation in TypeScript
- Define the Product Interface
interface Document {
open(): void;
save(): void;
close(): void;
}
- Concrete Products
class WordDocument implements Document {
open(): void {
console.log("Opening Word Document");
}
save(): void {
console.log("Saving Word Document");
}
close(): void {
console.log("Closing Word Document");
}
}
class PDFDocument implements Document {
open(): void {
console.log("Opening PDF Document");
}
save(): void {
console.log("Saving PDF Document");
}
close(): void {
console.log("Closing PDF Document");
}
}
class ExcelDocument implements Document {
open(): void {
console.log("Opening Excel Document");
}
save(): void {
console.log("Saving Excel Document");
}
close(): void {
console.log("Closing Excel Document");
}
}
- Creator Abstract Class
abstract class DocumentCreator {
public abstract createDocument(): Document;
public newDocument(): void {
const doc = this.createDocument();
doc.open();
doc.save();
doc.close();
}
}
- Concrete Creators
class WordDocumentCreator extends DocumentCreator {
public createDocument(): Document {
return new WordDocument();
}
}
class PDFDocumentCreator extends DocumentCreator {
public createDocument(): Document {
return new PDFDocument();
}
}
class ExcelDocumentCreator extends DocumentCreator {
public createDocument(): Document {
return new ExcelDocument();
}
}
- Client Code
class Application {
public static main(): void {
let creator: DocumentCreator;
creator = new WordDocumentCreator();
creator.newDocument();
creator = new PDFDocumentCreator();
creator.newDocument();
creator = new ExcelDocumentCreator();
creator.newDocument();
}
}
Application.main();
Explanation
Document Interface: This interface defines the methods
open(),save(), andclose()that all document types must implement.Concrete Products:
WordDocument,PDFDocument, andExcelDocumentare classes that implement theDocumentinterface. Each class provides its own implementation for the methods defined in the interface.DocumentCreator Abstract Class: This abstract class declares the factory method
createDocument(). It also provides anewDocument()method that calls the factory method to create a document and then performs a series of operations on it.Concrete Creators:
WordDocumentCreator,PDFDocumentCreator, andExcelDocumentCreatorare subclasses ofDocumentCreator. Each subclass implements thecreateDocument()method to instantiate a specific type of document.Client Code: The
Applicationclass demonstrates how to use the factory method pattern. It creates instances of different document creators and calls thenewDocument()method to generate and operate on documents.
Benefits of Using the Factory Method Pattern in TypeScript
Decoupling: The client code (
Application) does not need to know the exact class of the document it works with. It only interacts with theDocumentinterface and theDocumentCreatorabstract class.Single Responsibility: Each creator class is responsible for instantiating a specific type of document. The document classes handle their own specific behaviors.
Flexibility and Extensibility: Adding a new type of document is straightforward. You can create a new class that implements the
Documentinterface and a new creator class that extendsDocumentCreator.Maintainability: Changes in the creation process of specific documents do not affect the client code or other document types.
By using the Factory Method pattern, you can create huge apps with different features without complicating the code, adhering to principles of clean code and design patterns.
This content originally appeared on DEV Community and was authored by bilel salem
bilel salem | Sciencx (2024-06-20T22:42:39+00:00) Understanding the Factory Method Design Pattern. Retrieved from https://www.scien.cx/2024/06/20/understanding-the-factory-method-design-pattern/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.