Rspec-core: Update `rspec --init` so that it enables warnings in commented out `spec_helper` rather than in .rspec

[myronmarston]

...from a twitter conversation:

https://twitter.com/myronmarston/status/473646079280300032

[GeekOnCoffee]

Awesome. took a brief look to see if I could quickly figure out where this was happening, with little success... if nobody else gets to it, I'll try and dig in when I get a chance.

[myronmarston]

Basically, we just need to remove this line:

https://github.com/rspec/rspec-core/blob/91f428f609b37422c08306517e09d2466ab8e516/lib/rspec/core/project_initializer/.rspec#L2

...and add config.warnings = true to this file:

https://github.com/rspec/rspec-core/blob/master/lib/rspec/core/project_initializer/spec/spec_helper.rb

[JonRowe]

(Boo, I like forcing people to fix their warnings :P)

[myronmarston]

(Boo, I like forcing people to fix their warnings :P)

Unfortunately, many gems emit warnings, which can give the user a flood of messages without any indication what they can do to stop seeing them (since they can't change the warning-triggering code).

[JonRowe]

Yeah :/ although it might encourage them to go help fix them :P Or hassle the authors to do so :P

[myronmarston]

...or it might encourage users to not use RSpec when they can't figure out why they are getting so many warnings...

[jondlm]

This was definitely disturbing to me as a new rspec user. It didn't make me leave, but it definitely made me think I was doing something complete wrong. :+1: