Update modularity

.github/workflows/test.yml

@@ -0,0 +1,46 @@
+---
+name: Tests
+'on':
+  push:
+    branches:
+    - master
+  pull_request:
+    branches:
+    - master
+jobs:
+  test:
+    runs-on: ubuntu-24.04
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+        - ruby: 2.5.7
+          gemfile: Gemfile
+        - ruby: 2.6.10
+          gemfile: Gemfile
+        - ruby: 2.7.4
+          gemfile: Gemfile
+        - ruby: 3.0.2
+          gemfile: Gemfile
+        - ruby: 3.1.2
+          gemfile: Gemfile
+        - ruby: 3.2.1
+          gemfile: Gemfile
+        - ruby: 3.3.6
+          gemfile: Gemfile
+        - ruby: 3.4.1
+          gemfile: Gemfile
+    env:
+      BUNDLE_GEMFILE: "${{ matrix.gemfile }}"
+    steps:
+    - uses: actions/checkout@v2
+    - name: Install ruby
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: "${{ matrix.ruby }}"
+    - name: Bundle
+      run: |
+        gem install bundler:2.3.27
+        bundle install --no-deployment
+    - name: Run tests
+      run: bundle exec rspec

.gitignore

@@ -2,4 +2,3 @@ doc
 pkg
 *.gem
 .idea
-Gemfile.lock

.rspec

@@ -0,0 +1 @@
+--require spec_helper

.ruby-version

@@ -0,0 +1 @@
+2.5.7

CHANGELOG.md

@@ -0,0 +1,45 @@
+# Changelog
+All notable changes to this project will be documented in this file.
+
+This project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
+
+## Unreleased
+
+### Breaking changes
+
+### Compatible changes
+
+- Add support for Ruby 3.3
+- Add support for Ruby 3.4
+
+## 3.2.0 - 2023-03-01
+
+### Compatible changes
+
+- Add support for Ruby 3.2
+
+
+## 3.1.0 - 2022-06-01
+
+### Compatible changes
+
+- Add support for separation of positional and keyword arguments in ruby 3
+
+
+## 3.0.1 - 2022-03-09
+
+### Compatible changes
+
+- Activate Rubygems MFA
+
+
+## 3.0.0 - 2021-08-24
+
+### Breaking changes
+
+- Removed migration guide for modularity version 1.
+- Removed support for Ruby < `2.5.0`.
+
+### Compatible changes
+
+- Added this CHANGELOG file.

Gemfile

@@ -1,3 +1,8 @@
-source "http://rubygems.org"
+source 'http://rubygems.org'
 
 gemspec
+
+gem 'rake'
+gem 'rspec'
+gem 'pry-byebug'
+gem 'gemika'

Gemfile.lock

@@ -0,0 +1,47 @@
+PATH
+  remote: .
+  specs:
+    modularity (3.2.0)
+
+GEM
+  remote: http://rubygems.org/
+  specs:
+    byebug (11.1.3)
+    coderay (1.1.3)
+    diff-lcs (1.4.4)
+    gemika (0.8.1)
+    method_source (1.0.0)
+    pry (0.13.1)
+      coderay (~> 1.1)
+      method_source (~> 1.0)
+    pry-byebug (3.9.0)
+      byebug (~> 11.0)
+      pry (~> 0.13.0)
+    rake (13.0.6)
+    rspec (3.10.0)
+      rspec-core (~> 3.10.0)
+      rspec-expectations (~> 3.10.0)
+      rspec-mocks (~> 3.10.0)
+    rspec-core (3.10.1)
+      rspec-support (~> 3.10.0)
+    rspec-expectations (3.10.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.10.0)
+    rspec-mocks (3.10.2)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.10.0)
+    rspec-support (3.10.2)
+
+PLATFORMS
+  ruby
+  x86_64-linux
+
+DEPENDENCIES
+  gemika
+  modularity!
+  pry-byebug
+  rake
+  rspec
+
+BUNDLED WITH
+   2.3.27

LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2009 Henning Koch
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

README.md

@@ -0,0 +1,128 @@
+[![Tests](https://github.com/makandra/modularity/workflows/Tests/badge.svg)](https://github.com/makandra/modularity/actions)
+
+# Modularity - Traits and partial classes for Ruby
+
+Modularity enhances Ruby's [`Module`](http://apidock.com/ruby/Module) so it can be used traits and partial classes.
+This allows very simple definition of meta-programming macros like the
+`has_many` that you know from Rails.
+
+Modularity also lets you organize large models into multiple source files
+in a way that is less awkward than using modules.
+
+## Installation
+
+Add the following to your `Gemfile`:
+
+```ruby
+gem 'modularity'
+```
+
+Now run `bundle install`.
+
+## Example 1: Easy meta-programming macros
+
+Ruby allows you to construct classes using meta-programming macros like
+`acts_as_tree` or `has_many :items`. These macros will add methods,
+callbacks, etc. to the calling class. However, right now Ruby (and Rails) makes it awkward to define
+such macros in your project as part of your application domain.
+
+Modularity allows you to extract common behaviour into reusable macros by defining traits with parameters.
+Your macros can live in your application, allowing you to express your application domain in both classes
+and macros.
+
+Here is an example of a `strip_field` macro, which created setter methods that remove leading and trailing whitespace from newly assigned values:
+
+```ruby
+# app/models/article.rb
+class Article < ActiveRecord::Base
+  include DoesStripFields[:name, :brand]
+end
+
+# app/models/shared/does_strip_fields.rb
+module DoesStripFields
+  as_trait do |*fields|
+    fields.each do |field|
+      define_method("#{field}=") do |value|
+        self[field] = value.strip
+      end
+    end
+  end
+end
+```
+
+Notice the `as_trait` block.
+
+We like to add `app/models/shared` and `app/controllers/shared` to the load paths of our Rails projects.
+These are great places to store macros that are re-used from multiple classes.
+
+## Example 2: Mixins with class methods
+
+Using a module to add both instance methods and class methods is
+[very awkward](http://redcorundum.blogspot.com/2006/06/mixing-in-class-methods.html).
+Modularity does away with the clutter and lets you say this:
+
+```ruby
+# app/models/model.rb
+class Model
+  include Mixin
+end
+
+# app/models/mixin.rb
+module Mixin
+  as_trait do
+    def instance_method
+      # ...
+    end
+    def self.class_method
+      # ..
+    end
+  end
+end
+```
+
+`private` and `protected` will also work as expected when defining a trait.
+
+## Example 3: Splitting a model into multiple source files
+
+Models are often concerned with multiple themes like "authentication", "contact info" or "permissions", each requiring
+a couple of validations and callbacks here, and some method there. Modularity lets you organize your model into multiple
+partial classes, so each file can deal with a single aspect of your model:
+
+```ruby
+# app/models/user.rb
+class User < ActiveRecord::Base
+  include DoesAuthentication
+  include DoesPermissions
+end
+
+# app/models/user/does_authentication.rb
+module User::DoesAuthentication
+  as_trait do
+    # methods, validations, etc. regarding usernames and passwords go here
+  end
+end
+
+# app/models/user/does_permissions.rb
+module User::DoesPermissions
+  as_trait do
+    # methods, validations, etc. regarding contact information go here
+  end
+end
+```
+
+Some criticism has been raised for splitting large models into files like this.
+Essentially, even though have an easier time navigating your code, you will still
+have one giant model with many side effects.
+
+There are [many better ways](http://blog.codeclimate.com/blog/2012/10/17/7-ways-to-decompose-fat-activerecord-models/)
+to decompose a huge Ruby class.
+
+## Development
+
+* Install Bundler 2 `gem install bundler:2.2.22` and run `bundle install` to have a working development setup.
+* Running tests for the current Ruby version: `bundle exec rake`
+* Running tests for all supported Ruby version: Push the changes to Github in a feature branch, open a merge request and have a look at the test matrix in Github actions
+
+## Credits
+
+Henning Koch from [makandra.com](http://makandra.com/)