24 ms·
I think I made the decision a couple years ago that I'd rather just remember what the files should look like and create them as I need them. I work on varying t
by rubiquity 12y ago
I think I made the decision a couple years ago that I'd rather just remember what the files should look like and create them as I need them. I work on varying types of Rails apps (some full-on HTML/JS and others just JSON APIs) where a lot of times you don't need most of those files. I could see merit in just remembering the generator commands, though.
- lukeHeuer 12y agoI see. I'm on the same boat as far as developing varying types of apps w/ Rails. Disabling things I don't need, like asset pipeline for API dev is pretty quick: config.assets.enabled and config.generators.assets set to false and you don't have to worry about generators creating any unnecessary js/css in that scenario. Out of curiosity, what other things are being generated that wouldn't be of use?
- rubiquity 12y agoResource-based SCSS/CoffeeScript files. For an API I definitely don't need these, for a regular app I don't need them because I try to write JS/CSS around components rather than resources. Good call on just removing the generators though. I should just do that.