Comments on: Embracing Conventions With Namespaced Models And Partials

By: Derick Bailey

Derick Bailey — Thu, 12 May 2011 03:36:00 +0000

i ended up putting it into it’s own class in lib. i like the idea of putting it in helpers, though. i get really tired of having to restart the rails server every time i change something in lib. good suggestion. :)

By: Jak Charlton

Jak Charlton — Thu, 12 May 2011 03:10:00 +0000

Another small tip – anything in the Helpers folder will be loaded – regardless of file/module name

So removing that method from ApplicationHelper and putting it into it’s own module/file of (say) QuestionHelper would be neater

(ApplicationHelper should probably be deleted as the first step of creating a Rails application to stop it being a generic dumping ground)

By: Anonymous

Anonymous — Thu, 12 May 2011 02:20:00 +0000

Nice solution. I need to do something similar but with user ‘updates’ (twitter, forum post, etc). Each one is rendered differently but I really didn’t want to put the partial in the model itself. This is a good solution for that.

I like what you did even more because it isn’t “magic” in the hidden sense. If I need to know what partial is rendered its 100% clear that the ‘question_path’ function will answer the question.