Skip to content
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

chore: rubocop lint Metrics/ClassLength #944

Closed
wants to merge 6 commits into from

Conversation

iMacTia
Copy link
Member

@iMacTia iMacTia commented Mar 13, 2019

Description

See #854 - RuboCop linting

Fixes:

  • Metrics/ClassLength

Copy link
Member

@technoweenie technoweenie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What value does this PR give us, and especially, our users? We're currently working on releasing Faraday v1, a finished (or at least frozen) version of what users have been relying on for years. I don't think reorganizing the code to appease Rubocop is a good idea at this stage. It doesn't actually make Faraday work any better, but it does obscure the Git history of the moved code.

I would prefer tackling these code design issues in Faraday v2. New classes and modules can be extracted in separate PRs, without the strict constraint of maintaining backwards compatibility.

@iMacTia iMacTia closed this Mar 21, 2019
@iMacTia iMacTia deleted the fix/rubocop-class-length branch March 21, 2019 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants