Turns out, running rails destroy scaffold foo
from command line shows all files destroyed by the command — even if they don't exist. So rails destroy scaffold chocolatechip
(which I can assure you does not exist) results in:
invoke active_record
remove db/migrate/20150705235646_create_chocolatechip.rb
remove app/models/chocolatechip.rb
invoke test_unit
remove test/models/chocolatechip_test.rb
remove test/fixtures/chocolatechip.yml
invoke resource_route
route resources :chocolatechip
invoke responders_controller
remove app/controllers/chocolatechip_controller.rb
invoke erb
remove app/views/chocolatechip
remove app/views/chocolatechip/index.html.erb
remove app/views/chocolatechip/edit.html.erb
remove app/views/chocolatechip/show.html.erb
remove app/views/chocolatechip/new.html.erb
remove app/views/chocolatechip/_form.html.erb
invoke test_unit
remove test/controllers/chocolatechip_controller_test.rb
invoke helper
remove app/helpers/chocolatechip_helper.rb
invoke test_unit
invoke jbuilder
remove app/views/chocolatechip
remove app/views/chocolatechip/index.json.jbuilder
remove app/views/chocolatechip/show.json.jbuilder
invoke assets
invoke coffee
remove app/assets/javascripts/chocolatechip.coffee
invoke scss
remove app/assets/stylesheets/chocolatechip.scss
invoke scss
None of those files ever existed, but the aforementioned command shows them anyway. So basically, I never had a problem to begin with.