State Pattern

 

✅ Why we use the State Pattern (short)

• Avoids large if/else or switch blocks based on state
• Object behavior changes dynamically depending on its current state
• Follows clean design principles (Open/Closed, Single Responsibility)
• Makes code easier to maintain, extend, and test.
• Also validations can be done inside states ,and can prevent issues.
• Can also introduce new states, easily

✅ Key Idea

👉 Each state is a separate class

• DraftState, ReviewState, PublishedState, etc.
• Each class contains behavior specific to that state
• The main object (Context) just delegates work to the current state

🧠 One-line understanding

Instead of checking state with conditions, the object becomes the state by delegating to state classes.