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

Added a method that allows the generation of report without writing to a file #6

Merged

Conversation

nicwillemse
Copy link
Collaborator

Added a method that allows the generation of report without writing to a file

@nicwillemse nicwillemse closed this Apr 4, 2016
@nicwillemse nicwillemse reopened this Apr 4, 2016
@nicwillemse
Copy link
Collaborator Author

@cmckni3 any idea what the problem might be here ? This does not seem to be related to the code I have added ?

@cmckni3
Copy link
Owner

cmckni3 commented Apr 4, 2016

@nicwillemse Strange. This is actually a bundler error.


# Write file
def run_report(filename, &block)
Copy link
Owner

Choose a reason for hiding this comment

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

Excellent. This is the reason I reverted ffe38af. I wanted a separate method.

@nicwillemse
Copy link
Collaborator Author

@cmckni3 do you have any capacity to look at this now ?

@cmckni3
Copy link
Owner

cmckni3 commented Apr 4, 2016

@nicwillemse Thanks a lot for this contribution. I really meant to get around to making this change after I reverted ffe38af due to the control coupling.

The coupling made the method more complicated in my opinion and made testing a little awkward.

@cmckni3
Copy link
Owner

cmckni3 commented Apr 4, 2016

@nicwillemse I am doing a little investigation. If I can't figure it out in 15 minutes, I will have to wait about 8 hours.

@nicwillemse
Copy link
Collaborator Author

only a pleasure thanks @cmckni3 !

@cmckni3
Copy link
Owner

cmckni3 commented Apr 4, 2016

Running a new Travis build on the container infrastructure to see if it fixes the issue.

Strange that Ruby 2.0 didn't have an issue but 1.9.3 and 2.1 did.

@cmckni3
Copy link
Owner

cmckni3 commented Apr 4, 2016

@nicwillemse Can you rebase your changes on top of master? The build should pass on Travis after triggering a new build.

I will merge your changes after a rebase. 👍

@nicwillemse
Copy link
Collaborator Author

@cmckni3 - I have done a merge, I realise a rebase would have been better but there it is

@cmckni3
Copy link
Owner

cmckni3 commented Apr 4, 2016

👍

@cmckni3 cmckni3 merged commit 765736d into cmckni3:master Apr 4, 2016
@cmckni3
Copy link
Owner

cmckni3 commented Apr 4, 2016

Will create a new Rubygems release in the morning

@cmckni3
Copy link
Owner

cmckni3 commented Apr 4, 2016

Fixes #5

@nicwillemse
Copy link
Collaborator Author

Awesome - much appreciated @cmckni3

@cmckni3 cmckni3 mentioned this pull request Apr 4, 2016
@cmckni3
Copy link
Owner

cmckni3 commented Apr 4, 2016

Published 1.0.0 to rubygems

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