You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Hotel class is full of static methods, maybe you need share those methods. Single Responsibility Principle.
The whole program don't have extension for rooms, if the manager hotel needs change the rules business of rooms, he cannot. For this problem, I would create a interface "rooms" which contains a method that allow keep the extension. Open-Close Principle.
A DoubleRoom doesn't have polymorphism. Liskov Substitution Principle.
The Food class could be used for more of one service, better create a interface "Services" and then microservices for any room in the hotel. Interface Segregation Principle
The text was updated successfully, but these errors were encountered:
HI! this message is for educational purpose.
The Hotel class is full of static methods, maybe you need share those methods. Single Responsibility Principle.
The whole program don't have extension for rooms, if the manager hotel needs change the rules business of rooms, he cannot. For this problem, I would create a interface "rooms" which contains a method that allow keep the extension. Open-Close Principle.
A DoubleRoom doesn't have polymorphism. Liskov Substitution Principle.
The Food class could be used for more of one service, better create a interface "Services" and then microservices for any room in the hotel. Interface Segregation Principle
The text was updated successfully, but these errors were encountered: