shrek 0.2.1

Sign up to get free protection for your applications and to get access to all the features.
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: e1e94b489a95faebdcfb659d0d05cfff09f61c06db8a045879cab5069ec6e81b
4
+ data.tar.gz: 5322185041b996e16547cf01db847d45e9ba10acc8dee6c2765a2c5808e0c026
5
+ SHA512:
6
+ metadata.gz: 908cf284a79067aba046d1c9e078931ac9a7223d87605c1ea6753b5bf7be545225169fdff4865d6002f090ee0bba24f2c8287958374fc66b207b1988defd8d6a
7
+ data.tar.gz: f9257be0e9413dcd823caf44a4b4890b3801e147c98389dc3c94831742559a601c9d3b4a40fbdbe383b50f2f6d4f154892cfe0ae2da38a71e2a919ea33f66b73
@@ -0,0 +1,15 @@
1
+ /.bundle/
2
+ /.yardoc
3
+ /_yardoc/
4
+ /coverage/
5
+ /doc/
6
+ /pkg/
7
+ /spec/reports/
8
+ /tmp/
9
+ log/*.log
10
+ Gemfile.lock
11
+ *.gem
12
+ gemfiles/*.gemfile.lock
13
+
14
+ # rspec failure tracking
15
+ .rspec_status
@@ -0,0 +1,37 @@
1
+ # Use this file to configure the Overcommit hooks you wish to use. This will
2
+ # extend the default configuration defined in:
3
+ # https://github.com/brigade/overcommit/blob/master/config/default.yml
4
+ #
5
+ # At the topmost level of this YAML file is a key representing type of hook
6
+ # being run (e.g. pre-commit, commit-msg, etc.). Within each type you can
7
+ # customize each hook, such as whether to only run it on certain files (via
8
+ # `include`), whether to only display output if it fails (via `quiet`), etc.
9
+ #
10
+ # For a complete list of hooks, see:
11
+ # https://github.com/brigade/overcommit/tree/master/lib/overcommit/hook
12
+ #
13
+ # For a complete list of options that you can use to customize hooks, see:
14
+ # https://github.com/brigade/overcommit#configuration
15
+ #
16
+ # Uncomment the following lines to make the configuration take effect.
17
+
18
+ PreCommit:
19
+ RuboCop:
20
+ enabled: true
21
+ on_warn: fail # Treat all warnings as failures
22
+ AuthorName:
23
+ enabled: false
24
+ description: 'Check for author name'
25
+
26
+ #
27
+ # TrailingWhitespace:
28
+ # enabled: true
29
+ # exclude:
30
+ # - '**/db/structure.sql' # Ignore trailing whitespace in generated files
31
+ #
32
+ #PostCheckout:
33
+ # ALL: # Special hook name that customizes all hooks of this type
34
+ # quiet: true # Change all post-checkout hooks to only display output on failure
35
+ #
36
+ # IndexTags:
37
+ # enabled: true # Generate a tags file with `ctags` each time HEAD changes
data/.reek ADDED
@@ -0,0 +1,2 @@
1
+ IrresponsibleModule:
2
+ enabled: false
data/.rspec ADDED
@@ -0,0 +1,3 @@
1
+ --format documentation
2
+ --color
3
+ --require spec_helper
@@ -0,0 +1,8 @@
1
+ Metrics/LineLength:
2
+ Max: 120
3
+ Style/Documentation:
4
+ Enabled: false
5
+ Metrics/CyclomaticComplexity:
6
+ Max: 10
7
+ Metrics/BlockLength:
8
+ Max: 40
@@ -0,0 +1 @@
1
+ 2.5.1
@@ -0,0 +1,8 @@
1
+ sudo: false
2
+ language: ruby
3
+ rvm:
4
+ - 2.3
5
+ - 2.4
6
+ - 2.5
7
+
8
+ before_install: gem install bundler -v 1.16.0
@@ -0,0 +1,74 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as
6
+ contributors and maintainers pledge to making participation in our project and
7
+ our community a harassment-free experience for everyone, regardless of age, body
8
+ size, disability, ethnicity, gender identity and expression, level of experience,
9
+ nationality, personal appearance, race, religion, or sexual identity and
10
+ orientation.
11
+
12
+ ## Our Standards
13
+
14
+ Examples of behavior that contributes to creating a positive environment
15
+ include:
16
+
17
+ * Using welcoming and inclusive language
18
+ * Being respectful of differing viewpoints and experiences
19
+ * Gracefully accepting constructive criticism
20
+ * Focusing on what is best for the community
21
+ * Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behavior by participants include:
24
+
25
+ * The use of sexualized language or imagery and unwelcome sexual attention or
26
+ advances
27
+ * Trolling, insulting/derogatory comments, and personal or political attacks
28
+ * Public or private harassment
29
+ * Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ * Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behavior and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behavior.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviors that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account, or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
+ reported by contacting the project team at root_p@mail.ru. All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality with regard to the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at [http://contributor-covenant.org/version/1/4][version]
72
+
73
+ [homepage]: http://contributor-covenant.org
74
+ [version]: http://contributor-covenant.org/version/1/4/
data/Gemfile ADDED
@@ -0,0 +1,8 @@
1
+ # frozen_string_literal: true
2
+
3
+ source 'https://rubygems.org'
4
+
5
+ # git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
6
+
7
+ # Specify your gem's dependencies in shrek.gemspec
8
+ gemspec
@@ -0,0 +1,40 @@
1
+ # frozen_string_literal: true
2
+
3
+ # A sample Guardfile
4
+ # More info at https://github.com/guard/guard#readme
5
+
6
+ ## Uncomment and set this to only include directories you want to watch
7
+ # directories %w(app lib config test spec features) \
8
+ # .select{|d| Dir.exists?(d) ? d : UI.warning("Directory #{d} does not exist")}
9
+
10
+ ## Note: if you are using the `directories` clause above and you are not
11
+ ## watching the project directory ('.'), then you will want to move
12
+ ## the Guardfile to a watched dir and symlink it back, e.g.
13
+ #
14
+ # $ mkdir config
15
+ # $ mv Guardfile config/
16
+ # $ ln -s config/Guardfile .
17
+ #
18
+ # and, you'll have to watch "config/Guardfile" instead of "Guardfile"
19
+
20
+ # Note: The cmd option is now required due to the increasing number of ways
21
+ # rspec may be run, below are examples of the most common uses.
22
+ # * bundler: 'bundle exec rspec'
23
+ # * bundler binstubs: 'bin/rspec'
24
+ # * spring: 'bin/rspec' (This will use spring if running and you have
25
+ # installed the spring binstubs per the docs)
26
+ # * zeus: 'zeus rspec' (requires the server to be started separately)
27
+ # * 'just' rspec: 'rspec'
28
+
29
+ guard :rspec, cmd: 'bundle exec rspec' do
30
+ require 'guard/rspec/dsl'
31
+ dsl = Guard::RSpec::Dsl.new(self)
32
+
33
+ # RSpec files
34
+ rspec = dsl.rspec
35
+ watch(rspec.spec_helper) { rspec.spec_dir }
36
+ watch(rspec.spec_support) { rspec.spec_dir }
37
+ watch(rspec.spec_files)
38
+
39
+ watch(dsl.ruby.lib_files) { rspec.spec_dir }
40
+ end
@@ -0,0 +1,21 @@
1
+ The MIT License (MIT)
2
+
3
+ Copyright (c) 2018 Kvokka
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in
13
+ all copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
21
+ THE SOFTWARE.
@@ -0,0 +1,155 @@
1
+ [![Build Status](https://travis-ci.org/kvokka/shrek.svg?branch=master)](https://travis-ci.org/kvokka/shrek)
2
+ [![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)
3
+
4
+ # Shrek
5
+
6
+ [![Shrek](https://i.imgur.com/hlXgpWR.png)](https://www.youtube.com/watch?v=GZpcwKEIRCI)
7
+
8
+
9
+ Minimalistic variation of nested builder pattern. The most popular pattern
10
+ implementation is in `Rack::Middleware`. Extremely useful for organizing
11
+ heavy processing and encapsulate every piece of logic.
12
+
13
+ * Hint: perfect for achieving understanding, how Middleware works
14
+
15
+ ## Installation
16
+
17
+ Add this line to your application's Gemfile:
18
+
19
+ ```ruby
20
+ gem 'shrek'
21
+ ```
22
+
23
+ And then execute:
24
+
25
+ $ bundle
26
+
27
+ Or install it yourself as:
28
+
29
+ $ gem install shrek
30
+
31
+ ## Usage
32
+
33
+ Basic structure is `Layer`. Layer is self-sufficient piece of logic, which
34
+ in ideal circumstances does not depend on any other Layer.
35
+
36
+ Each `Layer` must have method `#call(*args)`, which must return an
37
+ array, `args` structure in one domain scope does not have to be identical, but
38
+ it is highly recommended.
39
+
40
+ ```
41
+ class MyAwesomeLayer < Shrek::Layers
42
+ def call(bilder, *args, **options) # Argument structure is up to you.
43
+ # do something before next layer
44
+ args = [bilder, *args, options]
45
+ next_layer.call(*args) # Run next execution Layer
46
+ # some post execution logic. If you add it, keep in mind, that you have to
47
+ # return args for the next Layer
48
+ rescue SomeError => e
49
+ # We can handle the error here and re-raise it for futher Layers
50
+ # in this order we can split messy error handling and keep everything clean
51
+
52
+ next_layer.skip(2).call(*args) # Skip 2 layers and run
53
+ next_layer.skip!(42).call(*args) # Laught version. Will Raise if stack is
54
+ # not enough
55
+ end
56
+ end
57
+ ```
58
+
59
+ You can see more
60
+ [examples](https://github.com/kvokka/shrek/blob/master/spec/shrek/runner_acceptance_spec.rb)
61
+
62
+ Then you will be able to use desired collection of Layers with
63
+ `Shrek[MyAwesomeLayer, AnotherOne].call(*initial_arguments)`
64
+
65
+ may be used in own classes
66
+ ```
67
+ class Paint
68
+ include Shrek
69
+ end
70
+
71
+ Paint.new.use_layers FindPaints, SelectWall, PrepareBrushes
72
+ ```
73
+
74
+ Let's summarize procs and cons of this concept:
75
+
76
+ ##### Procs
77
+
78
+ * Maximum encapsulation
79
+ * Easy reordering
80
+ * Each peace of logic handles only own part of the error
81
+ * Readable high level interface with minimal noise
82
+ * Standardize interface for one peace of domain logic
83
+ * Static analyzers will be happy
84
+ * Simple tests
85
+ * Well documented by someone else ;)
86
+
87
+ ##### Cons
88
+
89
+ * One more abstraction layer
90
+ * Can be over-engineering
91
+ * Requires more memory
92
+ * More code, more files
93
+
94
+ ### Why do I need it?
95
+
96
+ Lets try to put this little snippet of a tale into a code . Given:
97
+
98
+ > Shrek wants to eat something, and he decides to do a slug soup. He got
99
+ > slugs and then went to get some wood for the fireplace. When he came back
100
+ > he put the wood into the fireplace and tried to make fire. But he did not find
101
+ > matches, so he had to move the wood back. He then made shashimi from the
102
+ > slugs and ate as much as he could.He put the rest of the food into the fridge.
103
+
104
+ It is a simple business story, but think for a while, how will you solve it?
105
+ And keep in mind, that in the real world a lot of things can go wrong and you
106
+ want to be able to extend this story, when author decides, that Shrek also has
107
+ to try to find the lighter or add some swamp spices for better flavor (or
108
+ onion)
109
+
110
+ The simplest way is
111
+
112
+ ```
113
+ class ServiceKlass
114
+ def initialize(*)
115
+ # ...
116
+ end
117
+
118
+ def call
119
+ # ...
120
+ end
121
+ end
122
+ ```
123
+
124
+ But you will have to keep explicit error handler, and resolve all sort of
125
+ errors there. You will not be able to share one error between parts of the
126
+ service class, so you will do new error names or generalize errors (again, this
127
+ pattern is for big and heavy tasks). So the error handler will grow (May be you also
128
+ extract it ). At the end you will find yourself with a mess.
129
+ Do not believe me? Ok, take default `Rails::Middleware` and try to rewrite it
130
+ in procedural style this weekend (and do not plan anything else, you will have
131
+ lot's of fun ;)
132
+
133
+ Another way to handle this sort of problem is `composite` pattern (the first
134
+ example of this pattern, which came to me is `ActiveRecord::Migration`). It will
135
+ aim at the same goal, but also you will get DSL of the `composite`. Also you will
136
+ not be able to have the ability of error splitting. Usually it is suitable.
137
+
138
+
139
+ ## Development
140
+
141
+ 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.
142
+
143
+ 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).
144
+
145
+ ## Contributing
146
+
147
+ 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.
148
+
149
+ ## License
150
+
151
+ The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
152
+
153
+ ## Code of Conduct
154
+
155
+ 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).
@@ -0,0 +1,8 @@
1
+ # frozen_string_literal: true
2
+
3
+ require 'bundler/gem_tasks'
4
+ require 'rspec/core/rake_task'
5
+
6
+ RSpec::Core::RakeTask.new(:spec)
7
+
8
+ task default: :spec
@@ -0,0 +1,12 @@
1
+ #!/usr/bin/env ruby
2
+ # frozen_string_literal: true
3
+
4
+ require 'bundler/setup'
5
+ require 'shrek'
6
+
7
+ # You can add fixtures and/or initialization code here to make experimenting
8
+ # with your gem easier. You can also use a different console, if you like.
9
+
10
+ # (If you use this, don't forget to add pry to your Gemfile!)
11
+ require 'pry'
12
+ Pry.start
@@ -0,0 +1,8 @@
1
+ #!/usr/bin/env bash
2
+ set -euo pipefail
3
+ IFS=$'\n\t'
4
+ set -vx
5
+
6
+ bundle install
7
+
8
+ # Do any other automated setup that you need to do here
@@ -0,0 +1,17 @@
1
+ # frozen_string_literal: true
2
+
3
+ require 'shrek/version'
4
+ require 'shrek/runner'
5
+ require 'shrek/layers'
6
+
7
+ module Shrek
8
+ EMPTY_RETURN = proc { |*a| a }
9
+
10
+ module_function
11
+
12
+ def use_layers(*args)
13
+ Runner.new(*args)
14
+ end
15
+
16
+ singleton_class.send(:alias_method, :[], :use_layers)
17
+ end
@@ -0,0 +1,29 @@
1
+ # frozen_string_literal: true
2
+
3
+ module Shrek
4
+ class Layers
5
+ def initialize(next_layer_proc = nil)
6
+ next_layer_proc ||= EMPTY_RETURN
7
+ @next_layer = next_layer_proc
8
+ end
9
+
10
+ def call(*)
11
+ raise 'Layer subclasses must define #call'
12
+ end
13
+
14
+ def skip!(count = 1)
15
+ raise ArgumentError unless count.is_a?(Integer) || count <= 0
16
+ count.times.inject(self) { |acc, _| acc.next_layer }
17
+ end
18
+
19
+ def skip(count = 1)
20
+ skip! count
21
+ rescue NoMethodError => _error
22
+ EMPTY_RETURN
23
+ end
24
+
25
+ protected
26
+
27
+ attr_reader :next_layer
28
+ end
29
+ end
@@ -0,0 +1,28 @@
1
+ # frozen_string_literal: true
2
+
3
+ module Shrek
4
+ class Runner
5
+ attr_reader :layers, :options
6
+
7
+ def initialize(*layers, **options)
8
+ @options = options
9
+ parse_layers!(*layers)
10
+ end
11
+
12
+ def call(*args)
13
+ chain.call(*args)
14
+ end
15
+
16
+ private
17
+
18
+ def chain
19
+ layers.reverse.inject(EMPTY_RETURN) { |inner, outer| outer.new(inner) }
20
+ end
21
+
22
+ def parse_layers!(*layers)
23
+ # now we use all args as layers, but in future maybe will be convenient
24
+ # to add registry?
25
+ @layers = layers
26
+ end
27
+ end
28
+ end
@@ -0,0 +1,5 @@
1
+ # frozen_string_literal: true
2
+
3
+ module Shrek
4
+ VERSION = '0.2.1'
5
+ end
@@ -0,0 +1,41 @@
1
+
2
+ # frozen_string_literal: true
3
+
4
+ lib = File.expand_path('lib', __dir__)
5
+ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
6
+ require 'shrek/version'
7
+
8
+ Gem::Specification.new do |spec|
9
+ spec.name = 'shrek'
10
+ spec.version = Shrek::VERSION
11
+ spec.authors = ['Kvokka']
12
+ spec.email = ['kvokka@yahoo.com']
13
+
14
+ spec.summary = 'Nested code organizer.'
15
+ spec.description = 'Help to keep deeply nested code with similar structure'
16
+ spec.homepage = 'https://github.com/kvokka/shrek'
17
+ spec.license = 'MIT'
18
+
19
+ # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'
20
+ # to allow pushing to a single host or delete this section to allow pushing to any host.
21
+ raise 'RubyGems 2.0 or newer is required' unless spec.respond_to?(:metadata)
22
+ spec.metadata['allowed_push_host'] = 'https://rubygems.org'
23
+
24
+ spec.files = `git ls-files -z`.split("\x0").reject do |f|
25
+ f.match(%r{^(test|spec|features)/})
26
+ end
27
+ spec.bindir = 'exe'
28
+ spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
29
+ spec.require_paths = ['lib']
30
+
31
+ spec.add_development_dependency 'bundler', '~> 1.16'
32
+ spec.add_development_dependency 'rake', '~> 10.0'
33
+ spec.add_development_dependency 'rspec', '~> 3.0'
34
+
35
+ spec.add_development_dependency 'guard', '~> 2.14.0'
36
+ spec.add_development_dependency 'guard-rspec', '~> 4.7.0'
37
+ spec.add_development_dependency 'overcommit', '~> 0.44.0'
38
+ spec.add_development_dependency 'pry', '~> 0.11.0'
39
+ spec.add_development_dependency 'reek', '~> 4.8.0'
40
+ spec.add_development_dependency 'rubocop', '~> 0.54.0'
41
+ end
metadata ADDED
@@ -0,0 +1,191 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: shrek
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.2.1
5
+ platform: ruby
6
+ authors:
7
+ - Kvokka
8
+ autorequire:
9
+ bindir: exe
10
+ cert_chain: []
11
+ date: 2018-04-01 00:00:00.000000000 Z
12
+ dependencies:
13
+ - !ruby/object:Gem::Dependency
14
+ name: bundler
15
+ requirement: !ruby/object:Gem::Requirement
16
+ requirements:
17
+ - - "~>"
18
+ - !ruby/object:Gem::Version
19
+ version: '1.16'
20
+ type: :development
21
+ prerelease: false
22
+ version_requirements: !ruby/object:Gem::Requirement
23
+ requirements:
24
+ - - "~>"
25
+ - !ruby/object:Gem::Version
26
+ version: '1.16'
27
+ - !ruby/object:Gem::Dependency
28
+ name: rake
29
+ requirement: !ruby/object:Gem::Requirement
30
+ requirements:
31
+ - - "~>"
32
+ - !ruby/object:Gem::Version
33
+ version: '10.0'
34
+ type: :development
35
+ prerelease: false
36
+ version_requirements: !ruby/object:Gem::Requirement
37
+ requirements:
38
+ - - "~>"
39
+ - !ruby/object:Gem::Version
40
+ version: '10.0'
41
+ - !ruby/object:Gem::Dependency
42
+ name: rspec
43
+ requirement: !ruby/object:Gem::Requirement
44
+ requirements:
45
+ - - "~>"
46
+ - !ruby/object:Gem::Version
47
+ version: '3.0'
48
+ type: :development
49
+ prerelease: false
50
+ version_requirements: !ruby/object:Gem::Requirement
51
+ requirements:
52
+ - - "~>"
53
+ - !ruby/object:Gem::Version
54
+ version: '3.0'
55
+ - !ruby/object:Gem::Dependency
56
+ name: guard
57
+ requirement: !ruby/object:Gem::Requirement
58
+ requirements:
59
+ - - "~>"
60
+ - !ruby/object:Gem::Version
61
+ version: 2.14.0
62
+ type: :development
63
+ prerelease: false
64
+ version_requirements: !ruby/object:Gem::Requirement
65
+ requirements:
66
+ - - "~>"
67
+ - !ruby/object:Gem::Version
68
+ version: 2.14.0
69
+ - !ruby/object:Gem::Dependency
70
+ name: guard-rspec
71
+ requirement: !ruby/object:Gem::Requirement
72
+ requirements:
73
+ - - "~>"
74
+ - !ruby/object:Gem::Version
75
+ version: 4.7.0
76
+ type: :development
77
+ prerelease: false
78
+ version_requirements: !ruby/object:Gem::Requirement
79
+ requirements:
80
+ - - "~>"
81
+ - !ruby/object:Gem::Version
82
+ version: 4.7.0
83
+ - !ruby/object:Gem::Dependency
84
+ name: overcommit
85
+ requirement: !ruby/object:Gem::Requirement
86
+ requirements:
87
+ - - "~>"
88
+ - !ruby/object:Gem::Version
89
+ version: 0.44.0
90
+ type: :development
91
+ prerelease: false
92
+ version_requirements: !ruby/object:Gem::Requirement
93
+ requirements:
94
+ - - "~>"
95
+ - !ruby/object:Gem::Version
96
+ version: 0.44.0
97
+ - !ruby/object:Gem::Dependency
98
+ name: pry
99
+ requirement: !ruby/object:Gem::Requirement
100
+ requirements:
101
+ - - "~>"
102
+ - !ruby/object:Gem::Version
103
+ version: 0.11.0
104
+ type: :development
105
+ prerelease: false
106
+ version_requirements: !ruby/object:Gem::Requirement
107
+ requirements:
108
+ - - "~>"
109
+ - !ruby/object:Gem::Version
110
+ version: 0.11.0
111
+ - !ruby/object:Gem::Dependency
112
+ name: reek
113
+ requirement: !ruby/object:Gem::Requirement
114
+ requirements:
115
+ - - "~>"
116
+ - !ruby/object:Gem::Version
117
+ version: 4.8.0
118
+ type: :development
119
+ prerelease: false
120
+ version_requirements: !ruby/object:Gem::Requirement
121
+ requirements:
122
+ - - "~>"
123
+ - !ruby/object:Gem::Version
124
+ version: 4.8.0
125
+ - !ruby/object:Gem::Dependency
126
+ name: rubocop
127
+ requirement: !ruby/object:Gem::Requirement
128
+ requirements:
129
+ - - "~>"
130
+ - !ruby/object:Gem::Version
131
+ version: 0.54.0
132
+ type: :development
133
+ prerelease: false
134
+ version_requirements: !ruby/object:Gem::Requirement
135
+ requirements:
136
+ - - "~>"
137
+ - !ruby/object:Gem::Version
138
+ version: 0.54.0
139
+ description: Help to keep deeply nested code with similar structure
140
+ email:
141
+ - kvokka@yahoo.com
142
+ executables: []
143
+ extensions: []
144
+ extra_rdoc_files: []
145
+ files:
146
+ - ".gitignore"
147
+ - ".overcommit.yml"
148
+ - ".reek"
149
+ - ".rspec"
150
+ - ".rubocop.yml"
151
+ - ".ruby-version"
152
+ - ".travis.yml"
153
+ - CODE_OF_CONDUCT.md
154
+ - Gemfile
155
+ - Guardfile
156
+ - LICENSE.txt
157
+ - README.md
158
+ - Rakefile
159
+ - bin/console
160
+ - bin/setup
161
+ - lib/shrek.rb
162
+ - lib/shrek/layers.rb
163
+ - lib/shrek/runner.rb
164
+ - lib/shrek/version.rb
165
+ - shrek.gemspec
166
+ homepage: https://github.com/kvokka/shrek
167
+ licenses:
168
+ - MIT
169
+ metadata:
170
+ allowed_push_host: https://rubygems.org
171
+ post_install_message:
172
+ rdoc_options: []
173
+ require_paths:
174
+ - lib
175
+ required_ruby_version: !ruby/object:Gem::Requirement
176
+ requirements:
177
+ - - ">="
178
+ - !ruby/object:Gem::Version
179
+ version: '0'
180
+ required_rubygems_version: !ruby/object:Gem::Requirement
181
+ requirements:
182
+ - - ">="
183
+ - !ruby/object:Gem::Version
184
+ version: '0'
185
+ requirements: []
186
+ rubyforge_project:
187
+ rubygems_version: 2.7.6
188
+ signing_key:
189
+ specification_version: 4
190
+ summary: Nested code organizer.
191
+ test_files: []