I don't see any problem of using the tt extension (which is the one
recommend by Thor) but first I want to understand better the problem. Which
problem does these files cause? Would not the same problem happen with erb?
Does it happen because people try to compile the entire lib folder?

On Wed, Feb 24, 2016, 09:01 Chashmeet Singh notifications@github.com
wrote:

.erb files are for layouts mate
.rb for ruby
I guess its a bad idea renaming them to .rb.erb

—
Reply to this email directly or view it on GitHub
#23847 (comment).

@chashmeetsingh thanks, but I thought that a file that doesn't load by Ruby "should not" be named .rb

@rafaelfranca assume you have a Rails app and you'd like to pre-compile your .rb files (including gems). a simplest way to do this is to walk all of the gemspec.lib **/*.rb files.
users of such scenarios (with Warbler under JRuby) bump into an issue with some .rb files not being "really" Ruby and thus require careful excludes ... all of these files are seen from Rails' gems (at least reports only mentioned them so far) and it seems that they might not need to have the .rb extension

e.g. lib/rails/generators/active_record/model/templates/model.rb :

<% module_namespacing do -%>
module <%= class_path.map(&:camelize).join('::') %>
  def self.table_name_prefix
    '<%= namespaced? ? namespaced_class_path.join('_') : class_path.join('_') %>_'
  end
end
<% end -%>

have mostly used .rb.erb extension for such files, but I do not insist on having that extension

I see. I'm fine with renaming them.

OK thanks, will setup a PR - this affects several gems. is it acceptable if I use the .rb.erb name then?

.rb.tt is our preferred way.

OK

This issue has been automatically marked as stale because it has not been commented on for at least
three months.

The resources of the Rails team are limited, and so we are asking for your help.

If you can still reproduce this error on the 5-0-stable branch or on master,
please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions.

This issue has been automatically closed because of inactivity.

If you can still reproduce this error on the 5-0-stable branch or on master,
please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions.