DHH
Sun, 15 Oct 2006 15:52:11 -0700
> > class StoryController < ApplicationController > > def create > > @story = Story.new(params[:story]) > > # do some stuff to @story here... > > > > @story.save [EMAIL PROTECTED] won't be set, without the patch > > we're discussing. > > end > > end
This is the same example I see for with_scope over and over again, which troubles me greatly. I've only ever seen one example of with_scope that seemed reasonable. Mike Clark had something in his model class to merge multiple conditions into one. Even though that seemed sorta legit, I really don't like features that point people in the wrong direction 95% of the time. Having with_scope publicly available seems to be exactly that. I'm seriously considering that we should deprecate with_scope as a public method and make it private by 2.0. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---