super_module 1.2.0 → 1.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2417fe4ac87bcf7e975d971de2f86caa01f1f357
-  data.tar.gz: 305eda58e8250ce45e24af27325ba09f2f34c9f1
+  metadata.gz: 68d5daba9c77fe5ee84f024856002607eaa567fb
+  data.tar.gz: 0fdb3c4950a1ffa2fea44970561c2c688a355fb1
 SHA512:
-  metadata.gz: f4eea83f2a17b20dd8c40ab3f5e710f702c501936fea5782dbfb8295ee5c3a8a7889479d742777bbfa6151d8aa6ccfdc71ab4fdbd9431e2a13dbd4f0986f1f1a
-  data.tar.gz: 071b746e0e94003c5716724e9b51744986bd28c388492ed55284d9c65f8c445393d2688e2e8be0046b101bbb6bccaed75a97a472c2356c4b748012541efbad2a
+  metadata.gz: ad5348c682aa493a0a22196b16c976e8bbeb1708aaf912503408bc4731eba158009ce44100237be0c5843848fcbf85f77a289656a5e686e14990238c98594c09
+  data.tar.gz: c5727909276e62bbff1e9ac82399cefb683a089c17b5a017924a66b6b4794555746a3add17b0731f03f3f4c71b358f96b7367c70acfea3a71fa21c217428817e

data/README.md

@@ -1,19 +1,21 @@
-# <img src="https://raw.githubusercontent.com/AndyObtiva/super_module/master/SuperModule.jpg" alt="SuperModule" align="left" height="50" /> &nbsp; SuperModule 2 Beta (1.2.0)
+# <img src="https://raw.githubusercontent.com/AndyObtiva/super_module/master/SuperModule.jpg" alt="SuperModule" align="left" height="50" /> &nbsp; SuperModule 2 Beta (1.2.1)
 [![Gem Version](https://badge.fury.io/rb/super_module.svg)](http://badge.fury.io/rb/super_module)
 [![Build Status](https://api.travis-ci.org/AndyObtiva/super_module.svg?branch=master)](https://travis-ci.org/AndyObtiva/super_module)
 [![Coverage Status](https://coveralls.io/repos/AndyObtiva/super_module/badge.svg?branch=master)](https://coveralls.io/r/AndyObtiva/super_module?branch=master)
 [![Code Climate](https://codeclimate.com/github/AndyObtiva/super_module.svg)](https://codeclimate.com/github/AndyObtiva/super_module)
 
-Calling [Ruby](https://www.ruby-lang.org/en/)'s [`Module#include`](http://ruby-doc.org/core-2.2.1/Module.html#method-i-include) to mix in a module does not bring in class methods by default. This can come as quite a surprise whenever a developer attempts to include class methods via a module. Fortunately, Ruby does offer a solution in the form of implementing the hook method [`Module.included(base)`](http://ruby-doc.org/core-2.2.1/Module.html#method-i-included) [following a certain boilerplate code idiom](http://www.railstips.org/blog/archives/2009/05/15/include-vs-extend-in-ruby/). However, this solution can hinder code maintainability and productivity flow in a big production-environment project that takes advantage of many [mixins](http://en.wikipedia.org/wiki/Mixin) to model the business domain via composable object [traits](http://en.wikipedia.org/wiki/Trait_(computer_programming)). 
+Calling [Ruby](https://www.ruby-lang.org/en/)'s [`Module#include`](http://ruby-doc.org/core-2.2.1/Module.html#method-i-include) to mix in a module does not bring in class methods by default. This can come as quite the surprise when attempting to include class methods via a module. 
 
-[`ActiveSupport::Concern`](http://api.rubyonrails.org/classes/ActiveSupport/Concern.html) is a popular Rails library that attempts to ease some of the boilerplate pain by offering a [DSL](http://www.infoq.com/news/2007/06/dsl-or-not) layer on top of [`Module.included(base)`](http://ruby-doc.org/core-2.2.1/Module.html#method-i-included). Unfortunately, while it improves the readability of the code needed to include class methods, it supports the same boilerplate idiom, thus feeling no more than putting a band-aid on the problem.
+Ruby offers one workaround in the form of implementing the hook method [`Module.included(base)`](http://ruby-doc.org/core-2.2.1/Module.html#method-i-included) [following a certain boilerplate code idiom](http://www.railstips.org/blog/archives/2009/05/15/include-vs-extend-in-ruby/). Unfortunately, it hinders code maintainability and productivity with extra unnecessary complexity, especially in production-environment projects employing many [mixins](http://en.wikipedia.org/wiki/Mixin) (e.g. modeling business domain models with composable object [traits](http://en.wikipedia.org/wiki/Trait_(computer_programming))). 
 
-Fortunately, [SuperModule](https://rubygems.org/gems/super_module) comes to the rescue. By declaring your module as a `super_module`, it will automatically include class methods whenever it is mixed into a class or another module via [`Module#include`](http://ruby-doc.org/core-2.2.1/Module.html#method-i-include).
+Another workaround is [`ActiveSupport::Concern`](http://api.rubyonrails.org/classes/ActiveSupport/Concern.html), a Rails library that attempts to ease some of the boilerplate pain by offering a [DSL](http://www.infoq.com/news/2007/06/dsl-or-not) layer on top of [`Module.included(base)`](http://ruby-doc.org/core-2.2.1/Module.html#method-i-included). Unfortunately, while it helps improve readability a bit, it adds even more boilerplate idiom cruft, thus feeling no more than putting a band-aid on the problem.
+
+But do not fear, [SuperModule](https://rubygems.org/gems/super_module) comes to the rescue! By declaring your module as a `super_module`, it will simply behave as one would expect and automatically include class methods along with instance methods, without any further work needed.
 
 ## Introductory Comparison
 
 To introduce [SuperModule](https://rubygems.org/gems/super_module), here is a comparison of three different approaches for writing a
-<code>UserIdentifiable</code> module. 
+<code>UserIdentifiable</code> module, which includes ActiveModel::Model module as an in-memory alternative to ActiveRecord::Base superclass (Side-note: ActiveModel::Model is not needed when extending ActiveRecord::Base to connect to database.)
 
 #### 1) [self.included(base)](http://ruby-doc.org/core-2.2.1/Module.html#method-i-included)
 
@@ -21,8 +23,8 @@ To introduce [SuperModule](https://rubygems.org/gems/super_module), here is a co
 module UserIdentifiable
   include ActiveModel::Model
 
-  def self.included(base_klass)
-    base_klass.extend(ClassMethods)
+  def self.included(base)
+    base.extend(ClassMethods)
     base.class_eval do
       belongs_to :user
       validates :user_id, presence: true
@@ -290,6 +292,10 @@ In the future, [SuperModule](https://rubygems.org/gems/super_module) could perha
 
 ## What's New?
 
+### v2 Beta (v1.2.1)
+
+* Standalone super module usage (e.g. direct class method invocation)
+
 ### v2 Beta (v1.2.0)
 
 * New `super_module(name)` syntax

data/VERSION

@@ -1 +1 @@
-1.2.0
+1.2.1

data/lib/super_module.rb

@@ -50,7 +50,8 @@ def super_module(name=nil, &super_module_body)
       parent = SuperModule.__super_module_parent(name, initial_ancestor)
       module_name = name.to_s.split('::').last
       parent.const_set(module_name, new_super_module)
+      super_module_body = new_super_module.super_module_body
+      new_super_module.class_eval(&super_module_body)
     end
   end
 end
-

data/ruby187.Gemfile

@@ -7,11 +7,12 @@ group :development do
   gem "rdoc", "~> 4.2.0"
   gem "rspec", "~> 3.2.0"
 
-  # Ruby 1.8.7 support older gems
+  # Ruby 1.8.7 requires some older gems
   gem "mime-types", "~> 1.25.1"
   gem "netrc", "~> 0.9.0"
   gem "rest-client", "~> 1.6.0"
   gem "nokogiri", "~> 1.5.0"
   gem "highline", "~> 1.6.21"
+  gem "rake", "< 11.0"
 end
 

data/spec/lib/super_module_spec.rb

@@ -28,9 +28,19 @@ describe SuperModule do
     class BazActiveRecord < FakeActiveRecord
       include SupportVersion::Baz
     end
-    
+
     context version do
 
+      context "standalone module usage" do
+        subject { Support::V2::FakeActiveModel }
+
+        it 'allows invoking class methods' do
+          subject.validates 'foo', {:presence => true}
+          expect(subject.validations).to include(['foo', {:presence => true}])
+        end
+
+      end
+
       context "included by a module (Foo) that is included by a class (FooActiveRecord)" do
 
         subject { FooActiveRecord }

data/super_module.gemspec

@@ -2,17 +2,17 @@
 # DO NOT EDIT THIS FILE DIRECTLY
 # Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
 # -*- encoding: utf-8 -*-
-# stub: super_module 1.2.0 ruby lib
+# stub: super_module 1.2.1 ruby lib
 
 Gem::Specification.new do |s|
-  s.name = "super_module"
-  s.version = "1.2.0"
+  s.name = "super_module".freeze
+  s.version = "1.2.1"
 
-  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
-  s.require_paths = ["lib"]
-  s.authors = ["Andy Maleh"]
-  s.date = "2016-05-03"
-  s.description = "SuperModule allows defining class methods and method invocations the same way a super class does without using def included(base). This also succeeds ActiveSupport::Concern by offering lighter syntax"
+  s.required_rubygems_version = Gem::Requirement.new(">= 0".freeze) if s.respond_to? :required_rubygems_version=
+  s.require_paths = ["lib".freeze]
+  s.authors = ["Andy Maleh".freeze]
+  s.date = "2017-10-23"
+  s.description = "SuperModule allows defining class methods and method invocations the same way a super class does without using def included(base). This also succeeds ActiveSupport::Concern by offering lighter syntax".freeze
   s.extra_rdoc_files = [
     "LICENSE.txt",
     "README.md"
@@ -52,30 +52,45 @@ Gem::Specification.new do |s|
     "spec/support/v2_alt/foo.rb",
     "super_module.gemspec"
   ]
-  s.homepage = "http://github.com/AndyObtiva/super_module"
-  s.licenses = ["MIT"]
-  s.rubygems_version = "2.4.6"
-  s.summary = "SuperModule allows defining class methods and method invocations the same way a super class does without using def included(base). This also succeeds ActiveSupport::Concern by offering lighter syntax"
+  s.homepage = "http://github.com/AndyObtiva/super_module".freeze
+  s.licenses = ["MIT".freeze]
+  s.rubygems_version = "2.6.10".freeze
+  s.summary = "SuperModule allows defining class methods and method invocations the same way a super class does without using def included(base). This also succeeds ActiveSupport::Concern by offering lighter syntax".freeze
 
   if s.respond_to? :specification_version then
     s.specification_version = 4
 
     if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
-      s.add_runtime_dependency(%q<method_source>, ["~> 0.8.2"])
-      s.add_development_dependency(%q<jeweler>, ["~> 2.0.1"])
-      s.add_development_dependency(%q<rdoc>, ["~> 4.2.0"])
-      s.add_development_dependency(%q<rspec>, ["~> 3.2.0"])
+      s.add_runtime_dependency(%q<method_source>.freeze, ["~> 0.8.2"])
+      s.add_development_dependency(%q<jeweler>.freeze, ["~> 2.3.0"])
+      s.add_development_dependency(%q<rdoc>.freeze, ["~> 4.2.0"])
+      s.add_development_dependency(%q<rspec>.freeze, ["~> 3.2.0"])
+      s.add_development_dependency(%q<rake>.freeze, ["~> 10.4.2"])
+      s.add_development_dependency(%q<rack>.freeze, ["~> 1.6.5"])
+      s.add_development_dependency(%q<nokogiri>.freeze, ["~> 1.6.8.1"])
+      s.add_development_dependency(%q<tins>.freeze, ["~> 1.6.0"])
+      s.add_development_dependency(%q<term-ansicolor>.freeze, ["~> 1.3.2"])
     else
-      s.add_dependency(%q<method_source>, ["~> 0.8.2"])
-      s.add_dependency(%q<jeweler>, ["~> 2.0.1"])
-      s.add_dependency(%q<rdoc>, ["~> 4.2.0"])
-      s.add_dependency(%q<rspec>, ["~> 3.2.0"])
+      s.add_dependency(%q<method_source>.freeze, ["~> 0.8.2"])
+      s.add_dependency(%q<jeweler>.freeze, ["~> 2.3.0"])
+      s.add_dependency(%q<rdoc>.freeze, ["~> 4.2.0"])
+      s.add_dependency(%q<rspec>.freeze, ["~> 3.2.0"])
+      s.add_dependency(%q<rake>.freeze, ["~> 10.4.2"])
+      s.add_dependency(%q<rack>.freeze, ["~> 1.6.5"])
+      s.add_dependency(%q<nokogiri>.freeze, ["~> 1.6.8.1"])
+      s.add_dependency(%q<tins>.freeze, ["~> 1.6.0"])
+      s.add_dependency(%q<term-ansicolor>.freeze, ["~> 1.3.2"])
     end
   else
-    s.add_dependency(%q<method_source>, ["~> 0.8.2"])
-    s.add_dependency(%q<jeweler>, ["~> 2.0.1"])
-    s.add_dependency(%q<rdoc>, ["~> 4.2.0"])
-    s.add_dependency(%q<rspec>, ["~> 3.2.0"])
+    s.add_dependency(%q<method_source>.freeze, ["~> 0.8.2"])
+    s.add_dependency(%q<jeweler>.freeze, ["~> 2.3.0"])
+    s.add_dependency(%q<rdoc>.freeze, ["~> 4.2.0"])
+    s.add_dependency(%q<rspec>.freeze, ["~> 3.2.0"])
+    s.add_dependency(%q<rake>.freeze, ["~> 10.4.2"])
+    s.add_dependency(%q<rack>.freeze, ["~> 1.6.5"])
+    s.add_dependency(%q<nokogiri>.freeze, ["~> 1.6.8.1"])
+    s.add_dependency(%q<tins>.freeze, ["~> 1.6.0"])
+    s.add_dependency(%q<term-ansicolor>.freeze, ["~> 1.3.2"])
   end
 end
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: super_module
 version: !ruby/object:Gem::Version
-  version: 1.2.0
+  version: 1.2.1
 platform: ruby
 authors:
 - Andy Maleh
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-05-03 00:00:00.000000000 Z
+date: 2017-10-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: method_source
@@ -30,14 +30,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 2.0.1
+        version: 2.3.0
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 2.0.1
+        version: 2.3.0
 - !ruby/object:Gem::Dependency
   name: rdoc
   requirement: !ruby/object:Gem::Requirement
@@ -66,6 +66,76 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 3.2.0
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 10.4.2
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 10.4.2
+- !ruby/object:Gem::Dependency
+  name: rack
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.6.5
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.6.5
+- !ruby/object:Gem::Dependency
+  name: nokogiri
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.6.8.1
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.6.8.1
+- !ruby/object:Gem::Dependency
+  name: tins
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.6.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.6.0
+- !ruby/object:Gem::Dependency
+  name: term-ansicolor
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.3.2
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.3.2
 description: SuperModule allows defining class methods and method invocations the
   same way a super class does without using def included(base). This also succeeds
   ActiveSupport::Concern by offering lighter syntax
@@ -129,7 +199,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.6
+rubygems_version: 2.6.10
 signing_key: 
 specification_version: 4
 summary: SuperModule allows defining class methods and method invocations the same