-
-
Notifications
You must be signed in to change notification settings - Fork 357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor update_all_with_touch #279
Refactor update_all_with_touch #279
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
A word on commits: I am normally not a fan of squashing commits, and I like how you've made small atomic commits which make your refactoring process clear.
However, for such a small diff, having 14 commits will make it future "blaming" a little tedious. In this case, I think it would be beneficial to have them merged together.
If you agree, please squash them together and rebase against master if needed. But if you strongly feel inclined to keep the commits as they are, let me know.
Thanks @swanandp, we can actually do this for him with the Squash and merge button if you like? |
@brendon I am inclined to give him a choice. What do you think? |
Oh yes definitely. I was just meaning he doesn't have to do the squash himself if he wants it to go that way :) |
Hi,
I've refactored
update_all_with_touch
. If you're curious to know the reasons for my choices, I explain everything in a blog post: https://rubyclarity.com/2017/06/acts_as_list-refactoring-part-3/