I have two models like that
class Plan < ActiveRecord::Base
belongs_to :profile
And
class Profile < ActiveRecord::Base
has_many :plans
And routes like: (I need to)
resources :profiles do
resources :plans
end
resources :plans
So, following up ruby-on-rails – Problem with Nested Resources, I’ve made my PLANS index controller like this, to works NESTED and UNESTED at same time (the only way I’ve found for now):
def index
if params.has_key? :profile_id
@profile = Profile.find(params[:profile_id])
@plans = @profile.plans
else
@plans = Plan.all
end
There is a cleaner approach to this?
I have another models in this situation, and putting all actions, in all controllers to behave like this is cumbersome.
You gave me an idea:
models/user.rb:
models/post.rb:
controllers/posts_controller.rb:
And now the substance:
controllers/application_controller.rb:
The code is not complex to understand if you have notions of Ruby metaprogramming: it declares a before_filter which declares the instance variables inferring the names from the controller name and from the association. It is implemented just for the index actions, which is the only action using the plural instance variable version, but it should be easy to write a filter version for the other actions.