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 an Array 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.
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.