On Wed, Feb 11, 2009 at 2:52 PM, nat...@pivotalsf.com <nwil...@gmail.com> wrote:
> On Feb 10, 8:49 pm, David Chelimsky <dchelim...@gmail.com> wrote:
>> On Tue, Feb 10, 2009 at 2:02 PM, Nathan Wilmes <nat...@pivotallabs.com>
>> wrote:
>> > (2) The render override for RSpec controllers only takes one argument.
>> > This
>> > means that any controller using two argument forms will fail.
>>
>> > Our biggest use case for the two-argument controller form is this: render
>> > :update, :status => 404 do {}
>> > This case is still allowable and not deprecated in Rails 2.2.2.
>>
>> I can reinstate the extra arg. Are you looking for it to be handled in
>> some way? Or just to not blow up?
>
> It shouldn't blow up - right now it gives argument errors. It _ought_
> to behave identically to
> render :update => true, :status => 404 (Rails 2.2.2 converts the first
> form to the second).
Fixed. 2 down, 2 to go.
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
