Allow versions to be specified as an Array. #44
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.
So admittedly, this was a quick-and-dirty hack to get this working, but wanted to raise this issue since it has significant implications for anyone who is trying to follow semver. You need to be able to specify gem dependencies in the form
'~> x.y', '>= x.y.z'
if you want your gem dependency declarations to work for semver projects without breaking horribly anytime someone increments a minor version number.Obviously, this fix is going to do weird stuff if anyone provides anything but a
String
or anArray
value when they declare their dependencies and I'm not checking for that, however the cause of the problem ought to be obvious in that scenario.