devRant on iOS & Android lets you do all the things like
++ or -- rants, post your own rants and comment on others' rants. You can also set
up your profile. Get it now!
Free Swag!
Get a free stress ball if a rant you post gets 750 ++'s
In order to vote, comment or post rants, you need to confirm your email address.
You should have received a welcome email with a confirm link when you signed up. If you can't find the email, click the button below.
We've got two conflicting linters for ruby.
The rubocops serve the IDE and say to outdent access modifiers, giving the indented line a little yellow under-squiggle. Monkey see, monkey do, I indent it.
The company's one in the build pipeline wants to indent access modifiers and literally fails the bloody build, screaming about a rogue access modifier two spaces from where it should be.
Waste of 5 minutes.
Had something similar with autoformatters in a pre-commit hook.
During commit both would format the code and the commit would fail because of changes. After re-staging, the same would happen again, ad the first formatter reversed the second one partially and the second one this particular change of the first.
As soon as a change has been made by those formatters, the pre-commit-hook failed.
We've got two conflicting linters for ruby.
The rubocops serve the IDE and say to outdent access modifiers, giving the indented line a little yellow under-squiggle. Monkey see, monkey do, I indent it.
The company's one in the build pipeline wants to indent access modifiers and literally fails the bloody build, screaming about a rogue access modifier two spaces from where it should be.
Waste of 5 minutes.
rant