SOLID in Rails - Interface Segregation Principle


Many client specific interfaces are better than one general purpose interface.

We want to show or create Fee. It's the same method but with additional options - save or not, so we pass params true or false



But good way is divide this one action to different actions



Comments