summaryrefslogtreecommitdiff
path: root/bundler.gemspec
diff options
context:
space:
mode:
authorBundlerbot <bot@bundler.io>2019-07-06 15:01:34 +0000
committerBundlerbot <bot@bundler.io>2019-07-06 15:01:34 +0000
commit7ecc54af67b5b15a7467c296b0712df1acddfeb2 (patch)
treeb750fd90b3b4a6a89246e16d8548efa20f82f739 /bundler.gemspec
parent6ea383f8e2de364e72c3ac2c8be5cf688880e070 (diff)
parentf8584fb864fc2e7e2527d5ba2c50907a38328c92 (diff)
downloadbundler-7ecc54af67b5b15a7467c296b0712df1acddfeb2.tar.gz
Merge #7222
7222: Remove `add_development_dependency` from new gems r=deivid-rodriguez a=deivid-rodriguez ### What was the end-user problem that led to this PR? The problem was that a lot of gems in the wild use `add_development_dependency` for their development dependencies, but using `Gemfile`'s for that is more useful. ### What was your diagnosis of the problem? My diagnosis was that the current situation is due to the fact that bundler generates a gem skeleton that uses `add_development_dependency` by default. ### What is your fix for the problem, implemented in this PR? My fix is to stop using `add_development_dependency` in generated gems, and instead use the Gemfile. ### Why did you choose this fix out of the possible options? I chose this fix because it encourages better practices. Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
Diffstat (limited to 'bundler.gemspec')
0 files changed, 0 insertions, 0 deletions