I like them (in Rails) even though they add such little functionality. It's more about the concept of moving code from your models and controllers into separate files that contain a functionality in its entirety. Make those models small again :)
Serivce Objects and PORO is a must when you write a rake tasks. Processing the input and passing it to the service is all my rake tasks do. Much easier to test.
Auth With Twitter
Auth With GitHub
re: My Ruby Journey: Hooking Things Up VIEW POST
TOP OF THREAD FULL DISCUSSIONI like them (in Rails) even though they add such little functionality. It's more about the concept of moving code from your models and controllers into separate files that contain a functionality in its entirety. Make those models small again :)
I see! Definitely agree on slimming down. My company's go-to for slimming down model is always Service Objects, so that's what I've been used to.
I think one of these days I should definitely try out concerns! Thanks for sharing :)
Serivce Objects and PORO is a must when you write a rake tasks. Processing the input and passing it to the service is all my rake tasks do. Much easier to test.