This repository has been archived by the owner on Jan 8, 2025. It is now read-only.
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.
After adding this gem to a project, I noticed some weirdness around its dependencies:
This pull request cleans up the gemspec to deal with these issues. I am not familiar with jeweler at all, so I used their Rakefile and Gemfile as guides and could have messed something up.
This is what the dependency portion of the gemspec look like in current release (1.5.10):
This is what the dependencies look like with this patch applied: