Open Closed Principle
Information
The Open-Closed Principle (OCP) is a software design principle that suggests that classes, modules, and functions should be open for extension but closed for modification. This means that you should be able to add new features or behaviors to your software without changing the existing code.
You should make sure that it is easy to add new functionality without having to modify the existing code. This allows you to add new features or behaviors to your software without introducing bugs or breaking existing functionality.
The OCP encourages developers to create code that is easy to maintain and update over time. By following this principle, you will make your code more ready for change and reusable.
Dependency Inversion Principle describes a way to achieve OCP.
How to spot violation
- Abstraction and implementations are in same module
- Importing anything other than abstraction or external stuff(
/pkg, libraries) inside of implementations in/internal - Switch statements are suspicious, are you absolutely sure that you wont need to add new case in the future? Switches can be replaced with map lookups, which are more extensible and make code more data-driven
Resources
#principle