I’d say that is rubbish, since many editors create backup files, swap
files and other junk following some pretty well defined conventions.
Rails template compile code is very greedy and doesn’t care much about
extensions, even extensions it doesn’t understand. That is the bug.
Rails should not be the first application to completely ignore file
extensions and equate foo.html, foo.txt, foo.backup, foo.html.erb,
foo.rjs, foo.haml, foo.rhtml and foo.moved_out_the_way.html.erb as all
As a general principle, source control systems ignore these files and
so should rails. You are proposing that anything in the file tree is
100% fair game for Rails which would require many normal development
activities to be modified in inconvenient ways…
I was not suggesting that this is not a deficiency in Rails (I leave that discussion to others). I was suggesting that by not saving extraneous files in the project then the issue could be avoided. That is not rubbish, it is defensive programming.