Skip to content
This repository has been archived by the owner on Sep 27, 2023. It is now read-only.

Make repo rubocop compliant #20

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

n8chz
Copy link

@n8chz n8chz commented Oct 30, 2019

According to rubocop on default settings

Does "introduce rubocop" also entail adding rubocop to Gemfile?

According to rubocop on default settings
@Mehonoshin
Copy link
Member

@n8chz thanks for contribution!
yes, please, add rubocop to Gemfile, also add a blank .rubocop.yml to project.
And rebase you branch please

@Mehonoshin
Copy link
Member

Solves #18

@n8chz
Copy link
Author

n8chz commented Oct 30, 2019

Rubocop is in Gemfile for :test and :development, per line 24.

There is also already a .rubocop.yml at top level.

Blanking that out (assuming that's what's meant by 'standard style guide') results in 164 offenses. Correct these?

Note that default rubocop requires class documentation comments throughout. Have a style preference for those?

@Mehonoshin
Copy link
Member

@n8chz yes, please correct whatever is possible. You can leave only class documentation unresolved, I'll take care of them later.

Currently 33 offenses.
3 are for overly-long blocks.
Remainder are for lack of comments.
@Mehonoshin
Copy link
Member

@n8chz rebase your branch please

@n8chz
Copy link
Author

n8chz commented Nov 1, 2019

Is that as simple as git rebase or is the dreaded merge part of the process?

@Mehonoshin
Copy link
Member

@n8chz git rebase master, but make sure that you have the latest master before that.

@Mehonoshin
Copy link
Member

@n8chz or, as an alternative, you can just apply your rubocop config to a fresh branch, to avoid manual conflict resolution.

@n8chz
Copy link
Author

n8chz commented Nov 12, 2019

Clearly I'm in over my head here. Sorry.

@Mehonoshin
Copy link
Member

@n8chz okay, I'll take care of it.

@Mehonoshin Mehonoshin force-pushed the master branch 3 times, most recently from 4d3069b to bed5c11 Compare November 17, 2019 10:56
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants