On 29 Aug 2009, at 18:49, Adam Milligan wrote: > I'm not sure this is a Rails problem. Most web apps have an 'images' > directory under the public web root.
That's really kind of sidestepping the issue though. It's not just resources called 'images' that this happens to, and there's absolutely no requirement for template images to be stored in /images - they could be at another path, or on an asset server. +1 for allowing generators to pick up on any reserved keywords and warn about them. Obviously we can't catch everything, but it would be helpful to flag up names we know aren't going to work. -Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
