Comments for Kansas City on Rails

Comment on Nested Comments in Ruby on Rails, Part 1: Models by Febry Ramadhan

Febry Ramadhan — Wed, 19 Oct 2011 02:07:23 +0000

Nice!!

Comment on Nested Comments in Ruby on Rails, Part 1: Models by Bryan Jacobson (@BryanJacobson6)

Bryan Jacobson (@BryanJacobson6) — Wed, 07 Sep 2011 13:48:29 +0000

This was so helpful! Thank you so much!

Comment on Routing in Ruby on Rails 3 by saathi

saathi — Sun, 07 Aug 2011 05:05:34 +0000

Thanks. Helpful article

Comment on Routing in Ruby on Rails 3 by Andy

Andy — Wed, 01 Jun 2011 23:28:58 +0000

ok this is not a problem anymore.
if anybody get the same troubles, you’ll have to edit your views to the new routes structure presented here.
eg. you’d have to write %= link_to ‘Destroy’, post_comment_path(comment.post.id, comment.id), :confirm => ‘Are you sure?’, :method => :delete % instead of %= link_to ‘Destroy’, comment, :confirm => ‘Are you sure?’, :method => :delete %
*** Disclaimer: I’m like 90% noob and may be 100% wrong ;)

Comment on Routing in Ruby on Rails 3 by Andy

Andy — Wed, 01 Jun 2011 22:49:26 +0000

Hey bellmyer. First of all thank you very much for this post.
But as you may have guessed, almost nobody writes if everything ist fine. So to get it out: I looked at your github code and found out, that your controllers are structured in this nested way but your views are not.
Maybe this was your intention, anyway, i modified my comment’s index view to something like %= link_to ‘Show’, post_comment_path(comment.post.id, comment.id) % which is working… is this the way it should be done or am i wrong? i mean… sure i am showing a comment which is unique even without post.id, but then (with comment_path(comment.id)) there is an exeption “no controller found”, which is justified i guess.
i would be happy if you could clear my thoughts up a bit

Comment on Routing in Ruby on Rails 3 by Ogredude

Ogredude — Thu, 05 May 2011 00:58:29 +0000

When you’re using nested routes, make sure to change all form_for(@comment) to form_for([@post, @comment]) and all redirect_to(@comment) to redirect_to([@post, @comment])

It’s a bit different because we’ve got to pass a post object along with a comment object.

Also, link_to paths might need to be changed up, because we don’t have a comments_path, instead we have a post_comments_path, etc.

Comment on Adding Columns and Default Data to Existing Models by Rory Walker

Rory Walker — Sat, 16 Apr 2011 02:45:10 +0000

Thanks Jamie. Fixed my error :)

Comment on Show Intent with Better Naming by Jaime Bellmyer

Jaime Bellmyer — Fri, 11 Mar 2011 01:52:24 +0000

Wow, very true! Unlike self-documenting code or a working test suite, comments have no obligation to be accurate.

Comment on Show Intent with Better Naming by jim

jim — Thu, 10 Mar 2011 21:40:36 +0000

Cool post, I like the idea of showing intent in method names. This can help reduce comments and use self-documenting code instead. I’ve seen so many out-of-date misleading comments in old code that I rarely trust comments anymore.

Comment on Show Intent with Better Naming by Dan Carper

Dan Carper — Thu, 10 Mar 2011 21:40:03 +0000

I had the very same experience. Was at a code retreat hosted by Corey. Thought I had written some great code.. Took Corey 2 seconds to break my code but not my tests..

Good stuff!

Dan