Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Route concern and polymorphic model: how to share controller and views?

Given the routes:

Example::Application.routes.draw do
  concern :commentable do
    resources :comments
  end

  resources :articles, concerns: :commentable

  resources :forums do
    resources :forum_topics, concerns: :commentable
  end
end

And the model:

class Comment < ActiveRecord::Base
  belongs_to :commentable, polymorphic: true
end

When I edit or add a comment, I need to go back to the "commentable" object. I have the following issues, though:

1) The redirect_to in the comments_controller.rb would be different depending on the parent object

2) The references on the views would differ as well

= simple_form_for comment do |form|

Is there a practical way to share views and controllers for this comment resource?

like image 665
amencarini Avatar asked May 04 '13 15:05

amencarini


People also ask

What is polymorphic association in Ruby on Rails?

In Ruby on Rails, a polymorphic association is an Active Record association that can connect a model to multiple other models. For example, we can use a single association to connect the Review model with the Event and Restaurant models, allowing us to connect a review with either an event or a restaurant.

What resources do in Rails?

I would define a resource as a route which maps to related requests. So instead of declaring separate routes for the actions you want to do you can simply declare them using a resourceful route.In Rails, a resourceful route provides a mapping between HTTP requests and URLs to controller actions .

What is Rails routing?

The Rails router recognizes URLs and dispatches them to a controller's action, or to a Rack application. It can also generate paths and URLs, avoiding the need to hardcode strings in your views.


2 Answers

You can find the parent in a before filter like this:

comments_controller.rb

before_filter: find_parent

def find_parent
  params.each do |name, value|
    if name =~ /(.+)_id$/
      @parent = $1.classify.constantize.find(value)
    end
  end
end

Now you can redirect or do whatever you please depending on the parent type.

For example in a view:

= simple_form_for [@parent, comment] do |form|

Or in a controller

comments_controller.rb

redirect_to @parent # redirect to the show page of the commentable.
like image 87
Arjan Avatar answered Oct 14 '22 08:10

Arjan


In Rails 4 you can pass options to concerns. So if you do this:

# routes.rb
concern :commentable do |options|
  resources :comments, options
end


resources :articles do
  concerns :commentable, commentable_type: 'Article'
end

Then when you rake routes, you will see you get a route like

POST /articles/:id/comments, {commentable_type: 'Article'}

That will override anything the request tries to set to keep it secure. Then in your CommentsController:

# comments_controller.rb
class CommentsController < ApplicationController

  before_filter :set_commentable, only: [:index, :create]

  def create
    @comment = Comment.create!(commentable: @commentable)
    respond_with @comment
  end

  private
  def set_commentable
    commentable_id = params["#{params[:commentable_type].underscore}_id"]
    @commentable = params[:commentable_type].constantize.find(commentable_id)
  end

end

One way to test such a controller with rspec is:

require 'rails_helper'

describe CommentsController do

  let(:article) { create(:article) }

  [:article].each do |commentable|

    it "creates comments for #{commentable.to_s.pluralize} " do
      obj = send(commentable)
      options = {}
      options["#{commentable.to_s}_id"] = obj.id
      options["commentable_type".to_sym] = commentable.to_s.camelize
      options[:comment] = attributes_for(:comment)
      post :create, options
      expect(obj.comments).to eq [Comment.all.last]
    end

  end

end
like image 21
chris Avatar answered Oct 14 '22 06:10

chris