prototype option to run rspec with ruby warnings enabled#62
Conversation
|
loud, annoying, duck-like, voice |
|
lmao I think I'mma be done with the entire curriculum before this gets merged... |
|
Hey @ariccio! Thanks for opening this up. Running this by default is not likely something we can introduce. The That said, introducing the optional argument is potentially something we can do. I've added this PR to our internal planning for the learn-co gem suite. When we prepare the next release, we can take a closer look. That will likely be sometime within the next few months. Sorry for the delay! We really love to see participation in our OS work from students, so thanks again, and we'll keep you updated on this. |
|
Yeah, I bet it would cause some confusion, since some of the labs are themselves buggy 😆 On a serious note, I did spend hours in that first week debugging things that would've been caught by the warnings, so maybe it'd make new students more productive? |
I've added the option to run RSpec with Ruby warnings enabled. Personally, I'd love to see this enabled by default - I've found sketchy things in some of the specs for the labs I've been working on - but in the meantime, this does what I need it to do, and shouldn't be too controversial.
What do the maintainers think about running RSpec with warnings enabled by default?