shrek 0.2.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: e1e94b489a95faebdcfb659d0d05cfff09f61c06db8a045879cab5069ec6e81b
+  data.tar.gz: 5322185041b996e16547cf01db847d45e9ba10acc8dee6c2765a2c5808e0c026
+SHA512:
+  metadata.gz: 908cf284a79067aba046d1c9e078931ac9a7223d87605c1ea6753b5bf7be545225169fdff4865d6002f090ee0bba24f2c8287958374fc66b207b1988defd8d6a
+  data.tar.gz: f9257be0e9413dcd823caf44a4b4890b3801e147c98389dc3c94831742559a601c9d3b4a40fbdbe383b50f2f6d4f154892cfe0ae2da38a71e2a919ea33f66b73

data/.gitignore

@@ -0,0 +1,15 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+log/*.log
+Gemfile.lock
+*.gem
+gemfiles/*.gemfile.lock
+
+# rspec failure tracking
+.rspec_status

data/.overcommit.yml

@@ -0,0 +1,37 @@
+# Use this file to configure the Overcommit hooks you wish to use. This will
+# extend the default configuration defined in:
+# https://github.com/brigade/overcommit/blob/master/config/default.yml
+#
+# At the topmost level of this YAML file is a key representing type of hook
+# being run (e.g. pre-commit, commit-msg, etc.). Within each type you can
+# customize each hook, such as whether to only run it on certain files (via
+# `include`), whether to only display output if it fails (via `quiet`), etc.
+#
+# For a complete list of hooks, see:
+# https://github.com/brigade/overcommit/tree/master/lib/overcommit/hook
+#
+# For a complete list of options that you can use to customize hooks, see:
+# https://github.com/brigade/overcommit#configuration
+#
+# Uncomment the following lines to make the configuration take effect.
+
+PreCommit:
+  RuboCop:
+    enabled: true
+    on_warn: fail # Treat all warnings as failures
+  AuthorName:
+    enabled: false
+    description: 'Check for author name'
+
+#
+#  TrailingWhitespace:
+#    enabled: true
+#    exclude:
+#      - '**/db/structure.sql' # Ignore trailing whitespace in generated files
+#
+#PostCheckout:
+#  ALL: # Special hook name that customizes all hooks of this type
+#    quiet: true # Change all post-checkout hooks to only display output on failure
+#
+#  IndexTags:
+#    enabled: true # Generate a tags file with `ctags` each time HEAD changes

data/.reek

@@ -0,0 +1,2 @@
+IrresponsibleModule:
+  enabled: false

data/.rspec

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

data/.rubocop.yml

@@ -0,0 +1,8 @@
+Metrics/LineLength:
+  Max: 120
+Style/Documentation:
+  Enabled: false
+Metrics/CyclomaticComplexity:
+  Max: 10
+Metrics/BlockLength:
+  Max: 40

data/.ruby-version

@@ -0,0 +1 @@
+2.5.1

data/.travis.yml

@@ -0,0 +1,8 @@
+sudo: false
+language: ruby
+rvm:
+  - 2.3
+  - 2.4
+  - 2.5
+
+before_install: gem install bundler -v 1.16.0

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 root_p@mail.ru. 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/Gemfile

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

data/Guardfile

@@ -0,0 +1,40 @@
+# frozen_string_literal: true
+
+# A sample Guardfile
+# More info at https://github.com/guard/guard#readme
+
+## Uncomment and set this to only include directories you want to watch
+# directories %w(app lib config test spec features) \
+#  .select{|d| Dir.exists?(d) ? d : UI.warning("Directory #{d} does not exist")}
+
+## Note: if you are using the `directories` clause above and you are not
+## watching the project directory ('.'), then you will want to move
+## the Guardfile to a watched dir and symlink it back, e.g.
+#
+#  $ mkdir config
+#  $ mv Guardfile config/
+#  $ ln -s config/Guardfile .
+#
+# and, you'll have to watch "config/Guardfile" instead of "Guardfile"
+
+# Note: The cmd option is now required due to the increasing number of ways
+#       rspec may be run, below are examples of the most common uses.
+#  * bundler: 'bundle exec rspec'
+#  * bundler binstubs: 'bin/rspec'
+#  * spring: 'bin/rspec' (This will use spring if running and you have
+#                          installed the spring binstubs per the docs)
+#  * zeus: 'zeus rspec' (requires the server to be started separately)
+#  * 'just' rspec: 'rspec'
+
+guard :rspec, cmd: 'bundle exec rspec' do
+  require 'guard/rspec/dsl'
+  dsl = Guard::RSpec::Dsl.new(self)
+
+  # RSpec files
+  rspec = dsl.rspec
+  watch(rspec.spec_helper) { rspec.spec_dir }
+  watch(rspec.spec_support) { rspec.spec_dir }
+  watch(rspec.spec_files)
+
+  watch(dsl.ruby.lib_files) { rspec.spec_dir }
+end

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2018 Kvokka
+
+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,155 @@
+[![Build Status](https://travis-ci.org/kvokka/shrek.svg?branch=master)](https://travis-ci.org/kvokka/shrek) 
+[![Codacy Badge](https://api.codacy.com/project/badge/Grade/248c701de3be453298cefc5b481b47a2)](https://www.codacy.com/app/kvokka/shrek?utm_source=github.com&utm_medium=referral&utm_content=kvokka/shrek&utm_campaign=Badge_Grade)
+
+# Shrek
+
+[![Shrek](https://i.imgur.com/hlXgpWR.png)](https://www.youtube.com/watch?v=GZpcwKEIRCI)
+
+
+Minimalistic variation of nested builder pattern. The most popular pattern 
+implementation is in `Rack::Middleware`. Extremely useful for organizing 
+heavy processing and encapsulate every piece of logic.
+
+ * Hint: perfect for achieving understanding, how Middleware works
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'shrek'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install shrek
+
+## Usage
+
+Basic structure is `Layer`. Layer is self-sufficient piece of logic, which 
+in ideal circumstances does not depend on any other Layer.
+
+Each `Layer` must have method `#call(*args)`, which must return an 
+array,  `args` structure in one domain scope does not have to be identical, but
+it is highly recommended.
+
+```
+class MyAwesomeLayer < Shrek::Layers
+  def call(bilder, *args, **options)  # Argument structure is up to you.  
+    # do something before next layer
+    args = [bilder, *args, options]
+    next_layer.call(*args)            # Run next execution Layer
+    # some post execution logic. If you add it, keep in mind, that you have to 
+    # return args for the next Layer
+  rescue SomeError => e
+    # We can handle the error here and re-raise it for futher Layers
+    # in this order we can split messy error handling and keep everything clean
+    
+    next_layer.skip(2).call(*args)    # Skip 2 layers and run
+    next_layer.skip!(42).call(*args)  # Laught version. Will Raise if stack is
+                                      # not enough
+  end
+end
+```
+
+You can see more
+[examples](https://github.com/kvokka/shrek/blob/master/spec/shrek/runner_acceptance_spec.rb)
+
+Then you will be able to use desired collection of Layers with 
+`Shrek[MyAwesomeLayer, AnotherOne].call(*initial_arguments)`
+
+may be used in own classes
+```
+  class Paint
+    include Shrek
+  end
+  
+  Paint.new.use_layers FindPaints, SelectWall, PrepareBrushes
+```
+
+Let's summarize procs and cons of this concept:
+
+##### Procs
+
+* Maximum encapsulation
+* Easy reordering
+* Each peace of logic handles only own part of the error
+* Readable high level interface with minimal noise
+* Standardize interface for one peace of domain logic
+* Static analyzers will be happy
+* Simple tests
+* Well documented by someone else ;)
+
+##### Cons
+
+* One more abstraction layer
+* Can be over-engineering 
+* Requires more memory
+* More code, more files
+
+### Why do I need it?
+
+Lets try to put this little snippet of a tale into a code . Given:
+
+> Shrek wants to eat something, and he decides to do a slug soup. He got
+> slugs and then went to get some wood for the fireplace. When he came back
+> he put the wood into the fireplace and tried to make fire. But he did not find
+> matches, so he had to move the wood back. He then made shashimi from the
+> slugs and ate as much as he could.He put the rest of the food into the fridge.
+
+It is a simple business story, but think for a while, how will you solve it?
+And keep in mind, that in the real world a lot of things can go wrong and you
+want to be able to extend this story, when author decides, that Shrek also has
+to try to find the lighter or add some swamp spices for better flavor (or 
+onion)
+
+The simplest way is 
+
+```
+  class ServiceKlass
+    def initialize(*)
+      # ...
+    end 
+   
+    def call
+      # ...
+    end
+  end
+```
+
+But you will have to keep explicit error handler, and resolve all sort of 
+errors there. You will not be able to share one error between parts of the 
+service class, so you will do new error names or generalize errors (again, this
+pattern is for big and heavy tasks). So the error handler will grow (May be you also
+extract it ). At the end you will find yourself with a mess.
+Do not believe me? Ok, take default `Rails::Middleware` and try to rewrite it 
+in procedural style this weekend (and do not plan anything else, you will have
+lot's of fun ;)
+
+Another way to handle this sort of  problem is `composite` pattern (the first 
+example of this pattern, which came to me is `ActiveRecord::Migration`). It will
+aim at the same goal, but also you will get DSL of the `composite`. Also you will
+not be able to have the ability of error splitting. Usually it is suitable.
+
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem to your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/shrek. 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.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the Shrek project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/shrek/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,8 @@
+# frozen_string_literal: true
+
+require 'bundler/gem_tasks'
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new(:spec)
+
+task default: :spec

data/bin/console

@@ -0,0 +1,12 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require 'bundler/setup'
+require 'shrek'
+
+# 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

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/shrek.rb

@@ -0,0 +1,17 @@
+# frozen_string_literal: true
+
+require 'shrek/version'
+require 'shrek/runner'
+require 'shrek/layers'
+
+module Shrek
+  EMPTY_RETURN = proc { |*a| a }
+
+  module_function
+
+  def use_layers(*args)
+    Runner.new(*args)
+  end
+
+  singleton_class.send(:alias_method, :[], :use_layers)
+end

data/lib/shrek/layers.rb

@@ -0,0 +1,29 @@
+# frozen_string_literal: true
+
+module Shrek
+  class Layers
+    def initialize(next_layer_proc = nil)
+      next_layer_proc ||= EMPTY_RETURN
+      @next_layer = next_layer_proc
+    end
+
+    def call(*)
+      raise 'Layer subclasses must define #call'
+    end
+
+    def skip!(count = 1)
+      raise ArgumentError unless count.is_a?(Integer) || count <= 0
+      count.times.inject(self) { |acc, _| acc.next_layer }
+    end
+
+    def skip(count = 1)
+      skip! count
+    rescue NoMethodError => _error
+      EMPTY_RETURN
+    end
+
+    protected
+
+    attr_reader :next_layer
+  end
+end

data/lib/shrek/runner.rb

@@ -0,0 +1,28 @@
+# frozen_string_literal: true
+
+module Shrek
+  class Runner
+    attr_reader :layers, :options
+
+    def initialize(*layers, **options)
+      @options = options
+      parse_layers!(*layers)
+    end
+
+    def call(*args)
+      chain.call(*args)
+    end
+
+    private
+
+    def chain
+      layers.reverse.inject(EMPTY_RETURN) { |inner, outer| outer.new(inner) }
+    end
+
+    def parse_layers!(*layers)
+      # now we use all args as layers, but in future maybe will be convenient
+      # to add registry?
+      @layers = layers
+    end
+  end
+end

data/lib/shrek/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module Shrek
+  VERSION = '0.2.1'
+end

data/shrek.gemspec

@@ -0,0 +1,41 @@
+
+# frozen_string_literal: true
+
+lib = File.expand_path('lib', __dir__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'shrek/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = 'shrek'
+  spec.version       = Shrek::VERSION
+  spec.authors       = ['Kvokka']
+  spec.email         = ['kvokka@yahoo.com']
+
+  spec.summary       = 'Nested code organizer.'
+  spec.description   = 'Help to keep deeply nested code with similar structure'
+  spec.homepage      = 'https://github.com/kvokka/shrek'
+  spec.license       = 'MIT'
+
+  # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'
+  # to allow pushing to a single host or delete this section to allow pushing to any host.
+  raise 'RubyGems 2.0 or newer is required' unless spec.respond_to?(:metadata)
+  spec.metadata['allowed_push_host'] = 'https://rubygems.org'
+
+  spec.files = `git ls-files -z`.split("\x0").reject do |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', '~> 10.0'
+  spec.add_development_dependency 'rspec', '~> 3.0'
+
+  spec.add_development_dependency 'guard', '~> 2.14.0'
+  spec.add_development_dependency 'guard-rspec', '~> 4.7.0'
+  spec.add_development_dependency 'overcommit', '~> 0.44.0'
+  spec.add_development_dependency 'pry', '~> 0.11.0'
+  spec.add_development_dependency 'reek', '~> 4.8.0'
+  spec.add_development_dependency 'rubocop', '~> 0.54.0'
+end

metadata

@@ -0,0 +1,191 @@
+--- !ruby/object:Gem::Specification
+name: shrek
+version: !ruby/object:Gem::Version
+  version: 0.2.1
+platform: ruby
+authors:
+- Kvokka
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2018-04-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: '10.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.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'
+- !ruby/object:Gem::Dependency
+  name: guard
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 2.14.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 2.14.0
+- !ruby/object:Gem::Dependency
+  name: guard-rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 4.7.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 4.7.0
+- !ruby/object:Gem::Dependency
+  name: overcommit
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.44.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.44.0
+- !ruby/object:Gem::Dependency
+  name: pry
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.11.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.11.0
+- !ruby/object:Gem::Dependency
+  name: reek
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 4.8.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 4.8.0
+- !ruby/object:Gem::Dependency
+  name: rubocop
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.54.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.54.0
+description: Help to keep deeply nested code with similar structure
+email:
+- kvokka@yahoo.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- ".overcommit.yml"
+- ".reek"
+- ".rspec"
+- ".rubocop.yml"
+- ".ruby-version"
+- ".travis.yml"
+- CODE_OF_CONDUCT.md
+- Gemfile
+- Guardfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- lib/shrek.rb
+- lib/shrek/layers.rb
+- lib/shrek/runner.rb
+- lib/shrek/version.rb
+- shrek.gemspec
+homepage: https://github.com/kvokka/shrek
+licenses:
+- MIT
+metadata:
+  allowed_push_host: https://rubygems.org
+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.6
+signing_key: 
+specification_version: 4
+summary: Nested code organizer.
+test_files: []