I'm not sure that this is buggy behavior, which is why I did not post it over
there.  The question is if integrate_views should be a heritable trait or
not.  If it is, then we almost certainly need to be able to override it--and
as a convenience method, to be able to do so locally.  Implementing such a
scheme would involve a four-state @integrate_views -- heritably_no
(default), heritably_yes, heritably_yes_but_no_this_once, and
heritably_no_but_yes_this_once (current effect of calling integrate_views). 
Speaking of convenience, it would be nice to be able to set the value
globally.  And a pony.

Thanks



David Chelimsky-2 wrote:
> 
> On Wed, Mar 12, 2008 at 8:23 PM, nzook <[EMAIL PROTECTED]> wrote:
>>
>>  describe MyController do
>>   integrate_views
>>   describe "A common base senario" do
>>     it "no longer integrates views" do
>>       be_careful
>>    end
>>   end
>>  end
>>
>>  integrate_views affects an attribute in the class formed by the describe
>>  factory method.  The second describe generates its own class, so
>>  integrate_views is OFF at that level.  I've already spent far, far too
>> much
>>  time tracking this one down to verify that sub-describes at the same
>> level
>>  independently integrate_views (I expect that they should).
>>
>>  This might be a candidate for additional documentation.
> 
> I took the liberty of forwarding this to a ticket at lighthouse:
> 
> http://rspec.lighthouseapp.com/projects/5645/tickets/335
> _______________________________________________
> rspec-users mailing list
> rspec-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Warning%3A--integrate_views-and-nested-description-groups-tp16012571p16025037.html
Sent from the rspec-users mailing list archive at Nabble.com.

_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users

Reply via email to