ruby-mutant 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 51e7408e70faf6d2d947d56810cb097eb612234a92809ae92d1ba190cff3b976
+  data.tar.gz: d99ff9d4b8045ef89dc965081e872829cf08b8ceb313c04d3f48703ca54e1369
+SHA512:
+  metadata.gz: 5fdf4681e19da56d8e37edb0dc1289804eb98731193685777914831f7f94582491eab9f2ce788cd488c5495769806c5172a2da274da19bd1b0dbd10f17fdd74b
+  data.tar.gz: 19113031cd96afcc38351c4d6b8818a43ba712e100df8475bb11e9bdda21e32da0a247453bb35fef2dae2f63dc34809948a155a207323edd8bfbf6a14cb11d6e

data/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,23 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+
+
+**Additional context**
+Add any other context about the problem here.

data/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

data/.gitignore

@@ -0,0 +1,13 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+/.idea
+
+# rspec failure tracking
+.rspec_status
+.byebug_history

data/.rakeTasks

@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Settings><!--This file was automatically generated by Ruby plugin.
+You are allowed to: 
+1. Remove rake task
+2. Add existing rake tasks
+To add existing rake tasks automatically delete this file and reload the project.
+--><RakeGroup description="" fullCmd="" taksId="rake" /></Settings>

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.travis.yml

@@ -0,0 +1,7 @@
+---
+sudo: false
+language: ruby
+cache: bundler
+rvm:
+  - 2.5.1
+before_install: gem install bundler -v 1.16.6

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at TODO: Write your email address. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/CONTRIBUTING.md

@@ -0,0 +1,25 @@
+
+## How to contribute to RubyMutant
+---
+
+Did you find a bug?
+- Ensure the bug was not already reported by searching on Github under [issues](https://github.com/coreyjs/ruby-mutant/issues).
+- If you are unable to find any issue that is the same or address your problem, feel free to open a new bug report issue.  A clear and concise title and description of the bug and as much information possible on reproducible steps would greatly ensure the squashing of said bug.
+
+
+**Did you create a patch that fixes a bug?**
+- Open a new PR with the code fix
+- Ensure your PR description is clear and concise and describes the problem and the solution.  Include the issue # as well.
+- Make sure your patch has the appropriate test coverage to confirm the fix.
+- Once in review, a maintainer will review the PR and provide any needed feedback and guidance to help get the PR merged in.
+
+
+**Did you want to add a new feature or enhancement?**
+- Create a feature request using the "Feature Request" issue template, [here](https://github.com/coreyjs/ruby-mutant/issues/new?assignees=&labels=&template=feature_request.md&title=)
+- Be clear about the feature you want to add, the problem it is looking to solve or the idea/intent behind the feature.
+- If you plan to build the feature yourself, tag the issue with the label `work in progress` and assign yourself as an `Assignee` (or a maintainer can if permissions dont allow).
+- For branch naming conventions when dealing with features, please prefix the branch name with`feature/` such as  `feature/this-adds-async-support`
+- Once ready for review, open a PR with the base branch being `master`.  Once all builds are complete and passing, a maintainer will your with you to finalize any code changes that may be necessary.
+
+
+Thanks everyone for their interest in this project!  This is meant to be a learning expiernce for everyone, to learn how to contribute and work in open source.  I encourage you to pitch in and let your creativity drive you. ❤️❤️❤️

data/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in ruby-mutant.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,35 @@
+PATH
+  remote: .
+  specs:
+    ruby-mutant (0.0.4)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    diff-lcs (1.3)
+    rake (13.0.1)
+    rspec (3.8.0)
+      rspec-core (~> 3.8.0)
+      rspec-expectations (~> 3.8.0)
+      rspec-mocks (~> 3.8.0)
+    rspec-core (3.8.0)
+      rspec-support (~> 3.8.0)
+    rspec-expectations (3.8.2)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-mocks (3.8.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-support (3.8.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.16)
+  rake (~> 13.0)
+  rspec (~> 3.0)
+  ruby-mutant!
+
+BUNDLED WITH
+   1.17.3

data/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2018 Corey Schaf
+
+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.

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2018 TODO: Write your name
+
+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.

data/README.md

@@ -0,0 +1,152 @@
+# Ruby Mutant
+[![Build Status](https://travis-ci.org/coreyjs/ruby-mutant.svg?branch=master)](https://travis-ci.org/coreyjs/ruby-mutant)
+
+
+## Installation
+
+
+```ruby
+gem 'ruby-mutant', git: 'https://github.com/coreyjs/ruby-mutant'
+```
+
+---
+## Usage
+
+Ruby Mutant is a lightweight mutations library to help you encapsulate your business logic into decoupled, testable mutations.  With Ruby Mutant you can easily add executable code with validation, helping you decouple important logic from your application.
+
+To create a mutation from a ruby object, include the ruby module `require "mutatant"`  
+
+
+
+```ruby
+require "mutant"
+
+class RecipeCreatedMutation
+  include Mutant
+  
+  required_attr :recipe
+
+    #Define custom validators for our attributes
+    def validate_name?
+        true
+    end
+
+    # Required, this will execute our new mutation.
+    def execute(args)
+        # here, recipe is passe into out Class.run(recipe=Recipe.new) method
+        if recipe.difficulty == 'godlike'
+          recipe_service.send_alert_new_super_recipe_confirmation()
+        end 
+    end
+end
+```
+
+---
+To run a mutation definition:
+```ruby
+# run() excepts any number of parameters that you want to pass into your mutation
+output = RecipeCreatedMutation.run(recipe: Recipe.new, obj2: obj2, ....)
+```
+
+Every mutation execution will return an `output` object.  This object contains information on the
+mutation execution, and errors occurred or any metadata that's needed to be returned from the mutation, 
+in the form of a hash.
+
+Any meta data that needs to be returned can be added to the output object using the
+helper method inside your mutation:
+
+```ruby
+class RecipeCreatedMutation
+  include Mutant
+...
+    def execute(args)
+      output.add_meta(:test, 'value')
+    end
+
+...
+
+output = RecipeCreatedMutation.run()
+output.meta[:test] # >> 'value'
+
+```
+
+```ruby
+output = RecipeCreatedMutation.run(obj: obj1)
+output.success? # >> true
+output.errors # >>  [err1, err1, ...]
+output.meta # > {:my => 'value', :other => 'value1'}
+```
+
+---
+## How to use this library
+
+### Rails:
+We could define a folder structure such as this, for our rails Recipe web app:
+```
+/lib/use_cases/recipes/recipe_created_mutation.rb
+/lib/use_cases/user/new_user_signed_up_mutation.rb
+```
+
+`recipe_created_mutation.rb`
+```ruby
+require 'mutant'
+
+module UseCases::Recipes
+  class RecipeCreatedMutation
+    include Mutant
+
+    required_attr :recipe
+
+    def execute(args)
+      if recipe.name.blank?
+        puts 'whoops this recipe is bad'
+      end
+    end
+  end
+
+end
+```
+
+And in a controller, we can execute the mutation like so:
+
+```ruby
+class RecipesController < ApplicationController
+  include UseCases::Recipes
+
+ 
+    def create
+        @recipe = Recipe.new(recipe_params)
+        
+        output = RecipeCreatedMutation.run(recipe: @recipe)
+    
+        if output.success?
+          puts 'everything went super duper good'
+        end
+      end 
+
+...
+end
+```
+
+
+---
+
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/coreyjs/ruby-mutant. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+For more information on contributing, here:  [How To Contribute](https://github.com/coreyjs/ruby-mutant/blob/master/CONTRIBUTING.md)
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+
+## Special thanks to the inspiration for this library!
+
+https://github.com/cypriss/mutations
+
+https://github.com/omarish/mutations
+
+

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "ruby-mutant"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/lib/mutant.rb

@@ -0,0 +1,5 @@
+require "ruby-mutant/version"
+require "ruby-mutant/base"
+
+module Mutant
+end

data/lib/ruby-mutant/base.rb

@@ -0,0 +1,156 @@
+require 'ruby-mutant/exceptions/mutation_validation_exception'
+require 'ruby-mutant/exceptions/mutation_setup_exception'
+require 'ruby-mutant/exceptions/mutation_missing_required_var_exception'
+require 'ruby-mutant/output'
+require "bundler/setup"
+
+
+module Mutant
+    attr_accessor :output
+
+    def self.included(klass)
+        klass.extend(ClassMethods)
+    end
+
+    module ClassMethods
+        def required_attr(*attrs)
+            puts 'Mutant::required_attr'
+            # This defines a method called required_attr that will
+            # return an array of symbols for all the properties of the
+            # mutation that we should have defined.
+            define_method(:required_attr) { attrs ||= [] }
+        end
+
+        # The entry point, main method that will be execute any mutation logic
+        #
+        # == Parameters:
+        # args::
+        #   A hash of inputs suppplied when the user runs the mutation.
+        #   i.e. MyMutation.run(name: 'jon', house: 'stark')
+        #
+        # == Returns:
+        #   An instance of `Mutant::Output`.  This object defines all
+        #   errors, metadata and success definition of the mutation
+        def run(args = {})
+            unless args.has_key?(:raise_on_error)
+                args[:raise_on_error] = true
+            end
+            args[:raise_on_error].freeze
+
+            puts 'Mutant::self.run(*args) '
+            obj = new(args)
+
+            # Ensure the mutation has the correct method
+            unless obj.respond_to?(:execute)
+                raise MutationSetupException.new(msg='Missing execute method')
+            end
+
+            # 1. We want to run the validators first, then determine if we should continue
+            errs = obj.send(:validate)
+            obj.output.errors = obj.output.errors + errs
+            if errs.length > 0
+                if args[:raise_on_error]
+                    raise MutationSetupException.new(msg='Validation failed')
+                end
+            end
+
+            # 2. Check to see the mutation has the corresponding inst vars
+            args.each do |k, val|
+                puts "Mutant::var check '#{k}', responds? #{obj.respond_to? k.to_sym}"
+
+                # First make sure this mutation obj has the correct vars,
+                # if not, then proceeed to create them
+                unless obj.respond_to? k.to_sym
+                    # create the attr_accessor for the missing vars
+                    obj.class.send(:define_method, "#{k}=".to_sym) do |value|
+                        instance_variable_set("@" + k.to_s, value)
+                    end
+                    obj.class.send(:define_method, k.to_sym) do
+                        instance_variable_get("@" + k.to_s)
+                    end
+                end
+
+                # 3. Propagate the values from the mutation props to the class
+                obj.send("#{k}=".to_sym, val)
+            end
+
+            # 3 If this instance defines :required_attr
+            if obj.respond_to? :required_attr
+                required_attr_errors = obj.send(:check_required_attrs)
+                unless required_attr_errors.length == 0
+                    # We need to handle any errors we get back from our
+                    # required_attr validator
+                    obj.output.errors += required_attr_errors
+                    if args[:raise_on_error]
+                        raise required_attr_errors[0]
+                    end
+                end
+            end
+
+            # 4. Run execute method to run mutation logic
+            obj.execute(args)
+            # Return out Output obj, with all meta data regarding the ran mutation
+            obj.output
+        end
+    end
+
+    def initialize(*args)
+        @output = Output.new
+    end
+
+    private
+
+    # This will run all ou validation functions on our mutation class.
+    # This will return an array of MutationValidationException, to the class method, run()
+    #
+    # == Parameters:
+    #
+    # == Returns:
+    #  errors.  An array of errors representing all validation methods that have failed.
+    # (defaults to `[]`)
+    def validate
+        errors = []
+        self.public_methods.each do |m|
+            if m.to_s.start_with?('validate_') && m.to_s.end_with?('?')
+                # execute validation method
+                res = self.send(m)
+
+                # unless the response is truthy
+                unless res
+                    errors << MutationValidationException.new(msg='Validator has returned false', validator=m)
+                end
+            end
+        end
+        errors
+    end
+
+    # Checks to see if any `required_attr` has been set, if so check to see if each one
+    # is defined in either the .run() definition or the mutation's `attr_accesor`.
+    # TODO need to also check that these required attributes have values
+    #
+    # == Parameters:
+    #
+    # == Returns:
+    # An array of errors, of type `MutationMissingRequiredVarException`, for each
+    # missing required attribute.
+    def check_required_attrs
+        # In this we need to compare what we define in
+        # required_attr(*attrs) against what we have defined in
+        # the mutation vs what we pass into the run() definition
+        errors = []
+        puts 'Mutant::check_required_attrs'
+        self.required_attr.each do |attr|
+            if !self.respond_to?(attr)
+                # Our attribute is not defined on our mutation class
+                # So we will build the error to return to the run()
+                # method, which can determine how we proceed
+                err = MutationMissingRequiredVarException.new(
+                                    msg="A property that is marked as required is not defined on the mutation: #{attr}",
+                                    prop=attr)
+                errors << err
+            end
+        end
+        errors
+    end
+
+end

data/lib/ruby-mutant/exceptions/mutation_missing_required_var_exception.rb

@@ -0,0 +1,7 @@
+ class MutationMissingRequiredVarException < StandardError
+  attr_reader :prop
+  def initialize(msg='MutationMissingRequiredVarException', prop=nil)
+    @prop = prop
+    super("#{msg} - #{prop}")
+  end
+end

data/lib/ruby-mutant/exceptions/mutation_setup_exception.rb

@@ -0,0 +1,5 @@
+class MutationSetupException < StandardError
+  def initialize(msg='MutationSetupException')
+    super(msg)
+  end
+end

data/lib/ruby-mutant/exceptions/mutation_validation_exception.rb

@@ -0,0 +1,5 @@
+class MutationValidationException < StandardError
+    def initialize(msg='MutationValidationError', validator=nil)
+        super("#{msg} - #{validator}")
+    end
+end

data/lib/ruby-mutant/output.rb

@@ -0,0 +1,60 @@
+module Mutant
+    class Output
+
+        # Allows to reading the status of the executed mutation
+        attr_reader :success
+
+        # @return [Hash] the hash of metadata the user wants returned from the mutation execution
+        attr_accessor :meta
+
+        # @return [Array] The get/set for the mutations errors that have been thrown
+        attr_accessor :errors
+
+        # Output constructor
+        #
+        # == Parameters:
+        # success::
+        #   The successful state of the mutation that owns this object.  (defaults to `true`)
+        # errors::
+        #   An array of errors that can be packaged and wrapped in this object to be
+        #   `returned` from the mutation's `execute` method. (defaults to `[]`)
+        # meta::
+        #   A hash map that can be used to set any information that needs to be returned
+        #   from the mutation to the calling code.  (defaults to `{}`)
+        #
+        def initialize(success=true, errors=[], meta={})
+            @success = success
+            @errors = errors
+            @meta = meta
+        end
+
+        # Adds meta data to the @meta hash
+        # (will overwrite existing value)
+        #
+        # == Parameters:
+        # key::
+        #   A symbol that will be used to store the value in the hash
+        #
+        # value::
+        #   Any value that you wish to store indexed by the `key` param.
+        #   This can be used if you need to return data from the mutation's `execute` method
+        #
+        # == Returns:
+        #   Nothing useful
+        def add_meta(key, value)
+            @meta[key] = value
+        end
+
+        # Helper method to determine successfulnes of the mutation that has ran.  A successful
+        # mutation execution is defined by having an error count of 0.
+        # TODO:  This needs to be handled better, more smart about what success means
+        #
+        # == Parameters:
+        #
+        # == Returns:
+        #   A boolean that represents the status of the just execute mutation
+        def success?
+            @success
+        end
+    end
+end

data/lib/ruby-mutant/version.rb

@@ -0,0 +1,3 @@
+module Mutant
+    VERSION = "1.0.0"
+end

data/ruby-mutant.gemspec

@@ -0,0 +1,30 @@
+
+lib = File.expand_path("../lib", __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "ruby-mutant/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "ruby-mutant"
+  spec.version       = Mutant::VERSION
+  spec.authors       = ["Corey Schaf"]
+  spec.email         = ["cschaf@gmail.com"]
+
+  spec.summary       = %q{Clean up your code by encapsulating business logic in mutations!}
+  spec.description   = %q{Object mutations that encapsulate business logic.
+            RubyMutant makes it simple to add complex logic to objects, in with automatic validation and execution.}
+  spec.homepage      = "https://github.com/coreyjs/ruby-mutant"
+  spec.license       = "MIT"
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files         = Dir.chdir(File.expand_path('..', __FILE__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
+  end
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "bundler", "~> 1.16"
+  spec.add_development_dependency "rake", "~> 13.0"
+  spec.add_development_dependency "rspec", "~> 3.0"
+end

metadata

@@ -0,0 +1,112 @@
+--- !ruby/object:Gem::Specification
+name: ruby-mutant
+version: !ruby/object:Gem::Version
+  version: 1.0.0
+platform: ruby
+authors:
+- Corey Schaf
+autorequire:
+bindir: exe
+cert_chain: []
+date: 2021-05-01 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.16'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.16'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '13.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '13.0'
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+description: |-
+  Object mutations that encapsulate business logic.
+              RubyMutant makes it simple to add complex logic to objects, in with automatic validation and execution.
+email:
+- cschaf@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".github/ISSUE_TEMPLATE/bug_report.md"
+- ".github/ISSUE_TEMPLATE/feature_request.md"
+- ".gitignore"
+- ".rakeTasks"
+- ".rspec"
+- ".travis.yml"
+- CODE_OF_CONDUCT.md
+- CONTRIBUTING.md
+- Gemfile
+- Gemfile.lock
+- LICENSE
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- lib/mutant.rb
+- lib/ruby-mutant/base.rb
+- lib/ruby-mutant/exceptions/mutation_missing_required_var_exception.rb
+- lib/ruby-mutant/exceptions/mutation_setup_exception.rb
+- lib/ruby-mutant/exceptions/mutation_validation_exception.rb
+- lib/ruby-mutant/output.rb
+- lib/ruby-mutant/version.rb
+- ruby-mutant.gemspec
+homepage: https://github.com/coreyjs/ruby-mutant
+licenses:
+- MIT
+metadata: {}
+post_install_message:
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project:
+rubygems_version: 2.7.7
+signing_key:
+specification_version: 4
+summary: Clean up your code by encapsulating business logic in mutations!
+test_files: []