Come on now, that's a totally bogus analogy. The separation between M and VC is huge. You gain so incredibly much from having your models independent that there's absolutely no reason to support that.
The whole with_scope thing is much more nuanced. Please review my use case and tell me how it should be done. If you saw my whole architecture, you would see that giving Property any knowledge of User to work around this would just be ugly. Sending the method to Property is definitely the best solution unless there is some other avenue I haven't thought of. I just get this feeling that there's been this huge crackdown due to misuse without looking at the actual use cases where it might be justified. On 6/18/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote: > 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... > > > > > -- Gabe da Silveira http://darwinweb.net --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
