I noticed today, when I mistyped the keyword "references" as "reference" that rails g model doesn't enforce the types of attributes added to a model, so when the migration is run, an error occurs. Is there a reason this isn't enforced? Since generate model creates a migration by default, it would make sense for the rails command to catch errors like this before generating a bunch of files. Are there ever use cases where the you would want to pass an attribute type that wouldn't work in a migration, or is this a reasonable feature?
Thanks! -- 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+unsubscr...@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/d/optout.
