Joshua Flanagan
2014-Feb-08 03:00 UTC
Model generator should look for custom override in proper location
I went on quite an adventure today trying to override the template used by the model generator to create the migration file. Looks like at least one other person has had the same problem http://stackoverflow.com/questions/17389826/rails-overriding-migration-template The problem is that when the feature was added that let you generate a 'create table' migration independent of a model, it broke the search path for the template when using the model generator (https://github.com/rails/rails/commit/20e041579f5fe9df51bdc40048cc1ef78915e116). I've submitted a PR with a proposed fix, though I could use feedback on the approach https://github.com/rails/rails/pull/13972 -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscribe@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/groups/opt_out.