Thanks for your patience trying to resolve this issue. I posted a bug report here:
http://rubyforge.org/tracker/index.php?func=detail&aid=12963&group_id=797&atid=3149 On 8/10/07, David Chelimsky <[EMAIL PROTECTED]> wrote: > On 8/9/07, Lance Carlson <[EMAIL PROTECTED]> wrote: > > About these methods requiring arguments? I thought you were able to > > reproduce the problems I was having and was also able to reproduce a > > working application with no arguments. > > That is correct. > > > By default these methods should > > not require arguments to be passed as it is unnecessary noise in the > > code. > > I understand that, but that was news to me as of this thread. I spent > a couple of hours banging my head against this and found the generated > code I mentioned earlier in the thread. That's the only insight I have > to offer at this point. > > > Perhaps we can continue this discussion on IRC? #rspec? > > I'll pop in at one point this morning but I really don't have much in > the way of cycles to spend on this right now. I'm happy to help point > you in the right direction, but it's not very high on my priority > list. In the mean time, now that we know this is a bug, would you > kindly report it in the tracker? > > http://rubyforge.org/tracker/?atid=3149&group_id=797&func=browse > > > What is your s/n? > > > > On 8/9/07, David Chelimsky <[EMAIL PROTECTED]> wrote: > > > On 8/9/07, Lance Carlson <[EMAIL PROTECTED]> wrote: > > > > Is it possible that rspec is not pulling the instance variables into > > > > the method because this method is being defined before instance > > > > variables in parameters are assigned to that method? I'm trying to > > > > hone down where the problem is popping up exactly. Any insight? > > > > > > Not really more than what I said earlier in this thread. > > > > > > > On 8/9/07, David Chelimsky <[EMAIL PROTECTED]> wrote: > > > > > On 8/9/07, Lance Carlson <[EMAIL PROTECTED]> wrote: > > > > > > Were you able to come up with any solutions? > > > > > > > > > > Nope. Anyone else? > > > > > > > > > > > > > > > > > On 8/8/07, David Chelimsky <[EMAIL PROTECTED]> wrote: > > > > > > > On 8/8/07, Lance Carlson <[EMAIL PROTECTED]> wrote: > > > > > > > > Awesome! Thank you! :) > > > > > > > > > > > > > > Don't thank me yet. I've spent some time trying to track this > > > > > > > down and > > > > > > > I've found my way into some methods in routing.rb that are > > > > > > > dynamically > > > > > > > generated (and so you can't )(*&)(*& read them to debug them > > > > > > > quite so > > > > > > > easily) that call the methods (in your case) label_id_value and > > > > > > > id_value (being the artist id). I have no idea yet where those two > > > > > > > methods get generated. Once I do, then we can stub them. > > > > > > > Unfortunately > > > > > > > I can't really spend any more time on this right now (though I'd > > > > > > > love > > > > > > > to solve it). > > > > > > > > > > > > > > In the mean time, you'll just have to use the parameters if you > > > > > > > want > > > > > > > the specs to work with the same code with which your app works. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 8/8/07, David Chelimsky <[EMAIL PROTECTED]> wrote: > > > > > > > > > On 8/8/07, Lance Carlson <[EMAIL PROTECTED]> wrote: > > > > > > > > > > I just visited the action in my browser and i don't get any > > > > > > > > > > errors. I > > > > > > > > > > am also running on edge rails as the application relies on > > > > > > > > > > ActiveResource. Can you show me the code you created? > > > > > > > > > > > > > > > > > > OK - I've created a small project and am able to reproduce the > > > > > > > > > behaviour you're describing. I'll follow up when learn > > > > > > > > > something. > > > > > > > > > > > > > > > > > > David > > > > > > > > > _______________________________________________ > > > > > > > > > rspec-users mailing list > > > > > > > > > rspec-users@rubyforge.org > > > > > > > > > http://rubyforge.org/mailman/listinfo/rspec-users > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > rspec-users mailing list > > > > > > > > rspec-users@rubyforge.org > > > > > > > > http://rubyforge.org/mailman/listinfo/rspec-users > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > rspec-users mailing list > > > > > > > rspec-users@rubyforge.org > > > > > > > http://rubyforge.org/mailman/listinfo/rspec-users > > > > > > > > > > > > > _______________________________________________ > > > > > > rspec-users mailing list > > > > > > rspec-users@rubyforge.org > > > > > > http://rubyforge.org/mailman/listinfo/rspec-users > > > > > > > > > > > _______________________________________________ > > > > > rspec-users mailing list > > > > > rspec-users@rubyforge.org > > > > > http://rubyforge.org/mailman/listinfo/rspec-users > > > > > > > > > _______________________________________________ > > > > rspec-users mailing list > > > > rspec-users@rubyforge.org > > > > http://rubyforge.org/mailman/listinfo/rspec-users > > > > > > > _______________________________________________ > > > rspec-users mailing list > > > rspec-users@rubyforge.org > > > http://rubyforge.org/mailman/listinfo/rspec-users > > > > > _______________________________________________ > > rspec-users mailing list > > rspec-users@rubyforge.org > > http://rubyforge.org/mailman/listinfo/rspec-users > > > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
