0
kicks
Refactoring towards a DRY, fluent interface
In my current project, I have an application service that is used to make various modifications to a shopping cart, like adding cart items, applying discounts, changing quantities, etc. Well as this service class evolved, the methods were starting to look like this...