Type:
Module
A typical module looks like this:
1 2 3 4 5 6 7 8 9 10 11 12 | module M def self .included(base) base.extend ClassMethods base.class_eval do scope :disabled , -> { where(disabled: true ) } end end module ClassMethods ... end end |
By using ActiveSupport::Concern
the above module could instead
be written as:
1 2 3 4 5 6 7 8 9 10 11 12 13 | require 'active_support/concern' module M extend ActiveSupport::Concern included do scope :disabled , -> { where(disabled: true ) } end module ClassMethods ... end end |
Moreover, it gracefully handles module dependencies. Given a
Foo
module and a Bar
module which depends on the
former, we would typically write the following:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | module Foo def self .included(base) base.class_eval do def self .method_injected_by_foo ... end end end end module Bar def self .included(base) base.method_injected_by_foo end end class Host include Foo # We need to include this dependency for Bar include Bar # Bar is the module that Host really needs end |
But why should Host
care about Bar
's
dependencies, namely Foo
? We could try to hide these from
Host
directly including Foo
in Bar
:
1 2 3 4 5 6 7 8 9 10 | module Bar include Foo def self .included(base) base.method_injected_by_foo end end class Host include Bar end |
Unfortunately this won't work, since when Foo
is included,
its base
is the Bar
module, not the
Host
class. With ActiveSupport::Concern
, module
dependencies are properly resolved:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | require 'active_support/concern' module Foo extend ActiveSupport::Concern included do def self .method_injected_by_foo ... end end end module Bar extend ActiveSupport::Concern include Foo included do self .method_injected_by_foo end end class Host include Bar # works, Bar takes care now of its dependencies end |