How about a tutorial (better yet, a screencast) in the rails guides or wiki, by Rails version, of how the environment, plugins, and gems are loaded, and a list of common pitfalls. I've been using Rails since Jan '06 and the file loading process is still largely an unknown for me. And as you say, require_dependency and the like are not commented in the source, so you have to study the code to understand their intent. I didn't even know about require_or_load. In fact, would you mind explaining when you might want to use that method?
Luke On Sep 24, 10:01 am, Mateo Murphy <[email protected]> wrote: > I had figured the problem was something like that, and I think it > highlights a bigger issue: These types of errors are not uncommon, yet > the error messages are uninformative, and the solutions are not > officially documented. It would seem that require_or_load, > require_dependency and require_association are all meant for internal > use only, yet there seem to be situations where using them is the only > way to make things work. > > Any ideas on how to tackle this? > > On 21-Sep-09, at 5:09 PM, Luke wrote: > > > I found the solution, at least in my case. I have a class defined in > > test/mock/development that uses 'require' vs. 'require_dependency'. > > Changing to require_dependency fixed the problem, which I can > > understand. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
