-
Notifications
You must be signed in to change notification settings - Fork 0
change to leading dot configuration rather then trailing #6
Conversation
Yes, please. Easier to move them around. |
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.
Rejecting cause it doesn't meet current community standards. Are you sure, team? Can we talk about it? ;p
rubocop/ruby-style-guide#176
&&
|
We are MoneySmart community, we should have our own opinion and not following other people standard blindly. |
@wafendy these are community standards, it's good to use them because there will be new devs joining and they might be used to them as well. Also, I copied some valid arguments against this change in my previous comments. |
In expense of ignoring our argument why this works for us. |
@wafendy because of this change we won't be able to copy code blocks to irb/pry (which I think might be used quite often, at least I use it). I wish we could discuss it on the tech talk because the cons are quite high, so I wish everyone who approves it was familiar with what changes it brings. |
@BenR1312 are you ok to talk about it? :) |
That's a valid argument, then I'm ok to use the default setting. |
i got no problem with either, so long as we do it consistently. personal choice, i go with |
https://github.com/bbatsov/ruby-style-guide#consistent-multi-line-chains
the resolution to rubocop/ruby-style-guide#169 (comment) the resolution to the above is to actually include the idea that both styles are good and either is fine amongst the community @anna id like you to talk about this one at the tech talk in particular this is a good issue thats been raised and id rather not have to talk about other peoples issues for them at a tech talk. The reason why these PR's get put up in the first place is to act as a catalyst for discussion so if we think we need to talk about it further lets do that! |
We spoke about this at our Tech Talk and decided the benefits of the trailing dot far far outweigh the style preference of the leading dot. |
We run into this error a lot:
Place the . on the previous line, together with the method call receiver.
Rather then this:
im suggesting we go back to what everyone likes doing in the first place which was