Remove duplicated hash key in chart.rb#20
Merged
Conversation
The same hash key is on the line 29
This was referenced Jan 5, 2015
Closed
|
Looks like there are several other PRs duplicating this change. Since ansi is depended on by powerbar and minitest-reporters, it would be good to have this fix quickly since Ruby 2.2 complains about duplicate keys in hashes. Thanks in advance! |
Member
|
Oh no! I haven't been getting emails for pull requests for this project. Why? 😕 Will have to figure out and fix. Thanks for emailing me directly. I'll merge this and work my way through the other PRs. |
trans
added a commit
that referenced
this pull request
Jan 6, 2015
Remove duplicated hash key in chart.rb.
|
@trans, could this be released as 1.4.4 soon? Would like to get rid of: Thanks for your help! |
Member
|
Just released 1.5.0. Happy New Year! |
|
Thanks, @trans! Happy New Year! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The same hash key is on the line 29