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

update to ruby 2.6.3 #49

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

update to ruby 2.6.3 #49

wants to merge 3 commits into from

Conversation

Rovel
Copy link

@Rovel Rovel commented May 24, 2019

Hi I updated the gems and made some rubocop linters changes on some files.

rake safe running 100%

@Rovel Rovel mentioned this pull request Jul 18, 2019
@thirtysixthspan
Copy link
Owner

I've updated master to fix the build. If you rebase, your branch should run.

@@ -1,6 +1,6 @@
Gem::Specification.new do |s|
s.name = 'descriptive_statistics'
s.version = '2.5.1'
s.version = '2.5.2'
Copy link
Owner

@thirtysixthspan thirtysixthspan Jul 18, 2019

Choose a reason for hiding this comment

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

I'm only seeing development changes, not changes to the code of the gem itself, and so no version bump in warranted.

Copy link
Author

@Rovel Rovel Jul 19, 2019

Choose a reason for hiding this comment

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

ok, usually I do that in the patch to track any changes like updates and stuff so people can reference the new version or hold to the last they had running to avoid unwanted gem update at all. but if you prefer I can roll back the version.

end
end

def test_percentile_rank
@data.each do |test_case|
assert_equal test_case[0,10].percentile_rank(50).round(6), test_case[26].round(6)
assert_equal test_case[0, 10].percentile_rank(50).round(6), test_case[26].round(6)
Copy link
Owner

Choose a reason for hiding this comment

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

I would love to see rubocop implemented in this repository. Would you be open to moving any style related changes to a new pull request, one which included the rubocop package and a configuration?

Copy link
Author

@Rovel Rovel Jul 19, 2019

Choose a reason for hiding this comment

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

Sure, I will do that.
Any preference on the rubocop style guide or just the default one, one thing I would suggest is to increase the line size from 80 columns to something bigger specially for the test parts.

Copy link
Author

Choose a reason for hiding this comment

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

Hey, I opened the Rubocop PR as you asked, after merge we can work in the style changes 👓

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.

2 participants