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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nitpicker here, in the ruby world we indent with only two spaces.
As you're learning Rails, have a look at ActiveSupport::Concern, it's used quite a lot in more recent Rails apps.
Keep learning, I'm sure you'll enjoy programming Ruby :)
Oh yes definitely! I was copying it from multiple notes app and got messed up haha, thanks for pointing out!
What's your opinion on Concerns? I've heard a lot of people saying concerns are bad, but I've also seen DHH being a big advocate for it.
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 :)
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.