[rspec-devel] [ rspec-Patches-6393 ] [PATCH] rspec_on_rails uses deprecated '@response' instead of the accessor

David Chelimsky dchelimsky at gmail.com
Sun Oct 29 20:49:26 EST 2006


On 10/29/06, Wilson Bilkovich <wilsonb at gmail.com> wrote:
> On 10/29/06, noreply at rubyforge.org <noreply at rubyforge.org> wrote:
> > Patches item #6393, was opened at 2006-10-29 14:22
> > You can respond by visiting:
> > http://rubyforge.org/tracker/?func=detail&atid=3151&aid=6393&group_id=797
> >
> > Category: None
> > Group: None
> > Status: Open
> > Resolution: None
> > Priority: 3
> > Submitted By: Wilson Bilkovich (wilson)
> > Assigned to: Nobody (None)
> > Summary: [PATCH] rspec_on_rails uses deprecated '@response' instead of the accessor
> >
> > Initial Comment:
> > Pretty much what the summary says. This fixes deprecation warnings when running controller specs against edge rails.
> >
> > ----------------------------------------------------------------------
> >
> > You can respond by visiting:
> > http://rubyforge.org/tracker/?func=detail&atid=3151&aid=6393&group_id=797
> > _______________________________________________
>

These should all go away in 0.7.

> Right after this, I got a bunch more warnings about @session, etc,
> etc. This does fix the @response problem, but there are several more
> to track down.  I didn't see any mention of @session in the
> rspec_on_rails plugin code, so it might be some instance_variable_get
> magick.
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>


More information about the rspec-devel mailing list