This project is archived and is in readonly mode.
Optionally include copyright boilerplate in generated files
-
Ryan Bigg
I thought that a LICENSE file in the root of your project implied the license was for all files inside. I don't know why it needs to be at the top of every file, it just seems like useless garbage to me when I'm working on an application and I end up removing it.
-1
-
Ryan Bigg
- State changed from new to open
-
Lenary
This seems relatively astute, and not dangerous if you don't want to enable it through options.
That said, it might be an idea to look at how you could get thor to automatically do this with class extension or something via the ./lib directory.
Another avenue to look down would be completely custom generators, which you keep in a gem or repository. I'm not sure of the particulars of how rails 3 loads generators, but i'm sure you could investigate more!
All in all, I think this is probably a good feature, but not for core rails. This is what gems/plugins are for!
-1
-
Jeff Kreeftmeijer
Adding copyright information to the top of every file is the thing doesn't really sound DRY to me. I think it's perfect (and more DRY, for that matter) to just add a LICENCE file in your root. Also, I can't really see any reason why I would ever use this. Like Sam said though, put it in a gem! :)
-1
-
Josh Nesbitt
I don't really understand why you would want to add more line noise to every file. A LICENSE file should suffice. Put it into a gem?
-1
-
Ryan Bigg
- State changed from open to invalid
This has been downvoted by enough people that it's invalid.