concerning 1.0.1 → 1.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 3def6cff91fbf968ac2cfd3d096361a97a21c303
-  data.tar.gz: fdbcd11bcc90a557f31631fb05543b4c592697f3
+  metadata.gz: 454efdfc441f4945f845b6c1d73cbd5359c1d921
+  data.tar.gz: 1fb3b505754eed97217ae9661d152bec8ab2a674
 SHA512:
-  metadata.gz: 810cf85ce21d5e092342bcff876441d26616fba9b988f3bb64164d9f19d2beb8154f7bf85a2b118b298bba474b639f1c9b53286e339590e738fe88be0b6c0d5a
-  data.tar.gz: 3bf7542afd9315d2f9a72b6633bf836761ffefed0e520a1ea67a93daba875f99cdaeb12284f169db71e4effc66eb647a84f60c25acdc114ea1f8337e3aa4483f
+  metadata.gz: e8d1462bf277d70644c760e45947e76813bcea4f76ad7828959d4bf55ff75787ffa90cc0dfb283618ae4a32c8ea3ad6427b2ac4cb3cfd5588d773dad76a74fae
+  data.tar.gz: b0726d7cfdb19e3f0b1febc8dcbac4ffb3dc96a622fb31abd27a82ccc289402473a55b54b560309dbdffc675a38fb65ebc4e10d7231531c5fd5ecea3cfbcf506

data/lib/concerning.rb

@@ -1,126 +1,12 @@
-class Module
-  # We often find ourselves with a medium-sized chunk of behavior that we'd
-  # like to extract, but only mix in to a single class.
-  #
-  # We typically choose to leave the implementation directly in the class,
-  # perhaps with a comment, because the mental and visual overhead of defining
-  # a module, making it a Concern, and including it is just too great.
-  #
-  #
-  # Using comments as lightweight modularity:
-  #
-  #   class Todo
-  #     # Other todo implementation
-  #     # ...
-  #
-  #     ## Event tracking
-  #     has_many :events
-  #
-  #     before_create :track_creation
-  #     after_destroy :track_deletion
-  #
-  #     private
-  #       def track_creation
-  #         # ...
-  #       end
-  #   end
-  #
-  #
-  # Trying on a noisy embedded module:
-  #
-  #   class Todo
-  #     # Other todo implementation
-  #     # ...
-  #
-  #     module EventTracking
-  #       extend ActiveSupport::Concern
-  #
-  #       included do
-  #         has_many :events
-  #         before_create :track_creation
-  #         after_destroy :track_deletion
-  #       end
-  #
-  #       private
-  #         def track_creation
-  #           # ...
-  #         end
-  #     end
-  #     include EventTracking
-  #   end
-  #
-  #
-  # Once our chunk of behavior starts pushing the scroll-to-understand it
-  # boundary, we give in and move it to a separate file. At this size, the
-  # overhead feels in good proportion to the size of our extraction, despite
-  # diluting our at-a-glance sense of how things really work.
-  #
-  # Mix-in noise exiled to its own file:
-  #
-  #   class Todo
-  #     # Other todo implementation
-  #     # ...
-  #
-  #     include TodoEventTracking
-  #   end
-  #
-  #
-  # Introducing Module#concerning.
-  #
-  # By quieting the mix-in noise, we arrive at a natural, low-ceremony way to
-  # do bite-sized modularity:
-  #
-  #   class Todo
-  #     # Other todo implementation
-  #     # ...
-  #
-  #     concerning :EventTracking do
-  #       included do
-  #         has_many :events
-  #         before_create :track_creation
-  #         after_destroy :track_deletion
-  #       end
-  #
-  #       private
-  #         def track_creation
-  #           # ...
-  #         end
-  #     end
-  #   end
-  #
-  #   Todo.ancestors
-  #   # => Todo, Todo::EventTracking, Object
-  #
-  #
-  # This small step forward has some wonderful ripple effects. We can:
-  # * grok the behaviors that compose our class in one glance
-  # * clean up junk drawer classes by encapsulating their concerns
-  # * stop leaning on protected/private for "internal stuff" modularity
-  module Concerning
-    # Define a new concern and mix it in.
-    def concerning(topic, &block)
-      include concern(topic, &block)
-    end
-
-    # A low-cruft shortcut to define a concern.
-    #
-    #   concern :EventTracking do
-    #     ...
-    #   end
-    #
-    #   module EventTracking
-    #     extend ActiveSupport::Concern
-    #
-    #     ...
-    #   end
-    def concern(topic, &module_definition)
-      require 'active_support/concern'
-
-      const_set topic, Module.new {
-        extend ActiveSupport::Concern
-        module_eval(&module_definition)
-      }
-    end
-  end
-  include Concerning
+# This library was merged to Rails 4.1.
+#
+# Prefer Active Support's implementation if it's available.
+#
+# This allows libraries which support multiple Rails versions to depend on
+# `concerning` without worrying about implementation collision. This lib
+# will step aside if it sees its work is done.
+begin
+  require 'active_support/core_ext/module/concerning'
+rescue LoadError
+  require 'concerning/module_extension'
 end

data/lib/concerning/module_extension.rb

@@ -0,0 +1,147 @@
+class Module
+  # We often find ourselves with a medium-sized chunk of behavior that we'd
+  # like to extract, but only mix in to a single class.
+  #
+  # We typically choose to leave the implementation directly in the class,
+  # perhaps with a comment, because the mental and visual overhead of defining
+  # a module, making it a Concern, and including it is just too great.
+  #
+  #
+  # Using comments as lightweight modularity:
+  #
+  #   class Todo
+  #     # Other todo implementation
+  #     # ...
+  #
+  #     ## Event tracking
+  #     has_many :events
+  #
+  #     before_create :track_creation
+  #     after_destroy :track_deletion
+  #
+  #     def self.next_by_event
+  #       # ...
+  #     end
+  #
+  #     private
+  #       def track_creation
+  #         # ...
+  #       end
+  #   end
+  #
+  #
+  # Trying on a noisy embedded module:
+  #
+  #   class Todo
+  #     # Other todo implementation
+  #     # ...
+  #
+  #     module EventTracking
+  #       extend ActiveSupport::Concern
+  #
+  #       included do
+  #         has_many :events
+  #         before_create :track_creation
+  #         after_destroy :track_deletion
+  #       end
+  #
+  #       module ClassMethods
+  #         def next_by_event
+  #           # ...
+  #         end
+  #       end
+  #
+  #       private
+  #         def track_creation
+  #           # ...
+  #         end
+  #     end
+  #     include EventTracking
+  #   end
+  #
+  #
+  # Once our chunk of behavior starts pushing the scroll-to-understand it
+  # boundary, we give in and move it to a separate file. At this size, the
+  # overhead feels in good proportion to the size of our extraction, despite
+  # diluting our at-a-glance sense of how things really work.
+  #
+  # Mix-in noise exiled to its own file:
+  #
+  #   class Todo
+  #     # Other todo implementation
+  #     # ...
+  #
+  #     include TodoEventTracking
+  #   end
+  #
+  #
+  # Introducing Module#concerning.
+  #
+  # By quieting the mix-in noise, we arrive at a natural, low-ceremony way to
+  # do bite-sized modularity:
+  #
+  #   class Todo
+  #     # Other todo implementation
+  #     # ...
+  #
+  #     concerning :EventTracking do
+  #       included do
+  #         has_many :events
+  #         before_create :track_creation
+  #         after_destroy :track_deletion
+  #       end
+  #
+  #       class_methods do
+  #         def next_by_event
+  #           # ...
+  #         end
+  #       end
+  #
+  #       private
+  #         def track_creation
+  #           # ...
+  #         end
+  #     end
+  #   end
+  #
+  #   Todo.ancestors
+  #   # => Todo, Todo::EventTracking, Object
+  #
+  #
+  # This small step forward has some wonderful ripple effects. We can:
+  # * grok the behaviors that compose our class in one glance
+  # * clean up junk drawer classes by encapsulating their concerns
+  # * stop leaning on protected/private for "internal stuff" modularity
+  module Concerning
+    # Define a new concern and mix it in.
+    def concerning(topic, &block)
+      include concern(topic, &block)
+    end
+
+    # Add class methods via the concern.
+    def class_methods(&block)
+      const_set :ClassMethods, Module.new(&block)
+    end
+
+    # A low-cruft shortcut to define a concern.
+    #
+    #   concern :EventTracking do
+    #     ...
+    #   end
+    #
+    #   module EventTracking
+    #     extend ActiveSupport::Concern
+    #
+    #     ...
+    #   end
+    def concern(topic, &module_definition)
+      require 'active_support/concern'
+
+      const_set topic, Module.new {
+        extend ActiveSupport::Concern
+        module_eval(&module_definition)
+      }
+    end
+  end
+  include Concerning
+end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: concerning
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.0.2
 platform: ruby
 authors:
 - Jeremy Kemper
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-12-04 00:00:00.000000000 Z
+date: 2014-02-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -39,13 +39,14 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 description: 
-email: jeremy@37signals.com
+email: jeremy@basecamp.com
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
+- ./lib/concerning/module_extension.rb
 - ./lib/concerning.rb
-homepage: https://github.com/37signals/concerning
+homepage: https://github.com/basecamp/concerning
 licenses:
 - MIT
 metadata: {}
@@ -65,7 +66,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.0.14
+rubygems_version: 2.1.11
 signing_key: 
 specification_version: 4
 summary: Separating small concerns