Closed fbernier closed 9 years ago
Yeah. That's my fault. By convention/habit I always use -w
(warnings) but I also rarely do rails these days. All of my code is warning-free, so I never see any problems. Rails is also warning free, but many of the gems that rails uses (or people tend to use with rails) is not so you wind up with walls of junk like the above.
I need to make it accept -w
but not turn it on by default.
Looks like guard is almost your entire problem, btw... messy gem. Maybe you should file a bug?
Right, I guess not having -w by default would be best.
guard, SASS, factory_girl, jbuilder, devise ... and this project is still pretty new.
Feel free to close this whenever you want. Thanks!
Fixed.
Sorry for the huge dump but that's what I am getting when running it. Any idea why?