On Jun 11, 2008, at 11:55 AM, Ben Munat wrote: > > On the other hand, I like this just because I find the Ruby syntax > more > clearly indicates what you are doing, whereas the yaml is pure data > that > is sucked up into some mysterious place inside Rails. So I guess > that's > more than a "just because it's not yaml" reason. >
"No more YAML" is certainly the Reddit-friendly reason for this patch. Ousting YAML+ERB tricks is just the humane thing to do. :) However, the reason I really like this approach is that it cleans up clever configurations. People have been using File.exists? to figure out which MySQL socket to use within ERB blocks in database.yml for a long time. This makes those sorts of idioms easier to read and write. As the name of the patch implies, this approach is also considerably DRYer. If you want, you can define everything in environment.rb and move on. -- ~akk http://therealadam.com --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-core@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
