On 6/19/07, dasil003 <[EMAIL PROTECTED]> wrote: > > > Since when has Rails been about protecting programmers from themselves?
There were many fights about with_scope back when it was public. Rails is opinionated, and it is the opinion of the core team that it should become protected to ensure clean MVC. When you think about it, it makes sense. You can still leverage with_scope in your public model methods that accept a block. There were also people that wanted to be able to access sessions and controller params in their models. Naturally, the core team wouldn't allow that. Imagine what would happen if they did... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
