Rails 4 Controller Concern initializer

Question

I would like to add a status concern to various controllers since all of these controllers share the same status functionality.

A status can be "active", "inactive" or "archived". If added to a specific controller ex. bars_controller these methods would look like this:

def activate
  @bar.activate!
  redirect_to(:back)
end

def deactivate
  @bar.deactivate!
  redirect_to(:back)
end

def archive
  @bar.archive!
  redirect_to(:back)
end

I have moved the above to my concern called Foo and I've included Foo in my controller like this:

include Foo

The issue I have when moving these methods to a concern, is that the Model instance is not defined.

How do I generalize the "@bar" section of the code in my concern? This will enable me to use the concern for multiple Model instances including Baz. I tried using "self" but that references the Controller instance and not the Model instance.

If I understood this right, you will need to initialize this @bar somewhere. Since you are using it in many controllers do it in application controller. — Karan Purohit
– Karan Purohit, Commented Apr 3, 2015 at 12:24
Where is your @bar defined? You should have a method like def find_bar @bar = Bar.find(params[:id]); end somewhere. — pierallard
– pierallard, Commented Apr 3, 2015 at 12:53
@ForgetTheNorm, "bar" is defined in a "before_action". The "bar" is not an issue if it is in a specific controller itself. The problem arises when I move these methods to a more generic concern. I can't call "bar" in the concern as I need to use the Concern for "baz" as well. — HermannHH
– HermannHH, Commented Apr 3, 2015 at 13:17

kjmagic13 · Accepted Answer · 2015-08-04 20:01:14Z

1

Your concern could look like this:

module Foo
    extend ActiveSupport::Concern

    def activate
        render text: bar.to_json
    end

    def deactivate
        render text: bar.to_json
    end

    def archive
        render text: bar.to_json
    end

    private

    def bar
        # 'demodulize' isn't necessary if you're working outside of namespaces
        params[:controller].classify.demodulize.constantize.find(params[:id])
    end

end

And your routes would benefit from using a concern as well:

concern :statusable do
    member do
        get :activate
        get :deactivate
        get :archive
    end
end

resources :alphas, :bravos, :charlies, concerns: :statusable

answered Aug 4, 2015 at 20:01

kjmagic13

1,3288 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Rails 4 Controller Concern initializer

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related