interactify 0.1.0.pre.alpha.1 → 0.3.0.pre.RC1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7bbf811a8d9e44f85d4e0c5b36f4ad3291cbc8f5aa52e5d2dd31ecbdd753a256
-  data.tar.gz: 92ed7413e2ea370d388c43d9993928652d9bc23a3139d3fa083050243bc30695
+  metadata.gz: 319dd56313d82aa987c8eaec40691e43c58e8b72513969e2a6a7a83de17ae311
+  data.tar.gz: 3f5e4ad0464157910bca7bfd1300fa8e23ab825068c84a4c5c0ef5ad0cdb29d6
 SHA512:
-  metadata.gz: 1d9e01fc12b9b02bdc9d897b81866c7d668f94cf0fafd51e018cded3ec2892d5452848000672a9c4ac139f1c1dc3d30aa23e1c16b0dcaf66afd901c4586d8eae
-  data.tar.gz: b33dc94b10b26cf1b4baeace46168641d88121bf05fe2a4c8c37098d3b5bc678667e0ff253f620def1798846b9b95533f943ef4c80726abe08a1a41662c338c0
+  metadata.gz: fea0120a4456f108b41ccd48c994e365762bad8ff6424eba9d7ecd0c09c6858805e0456df0655eec86042ed7dc9fa589ffb8f3bdb49a14e79a7e05e30b6737ae
+  data.tar.gz: 64345da2e8b036ad65c639bddb9c0f90f93b1fdbc1415a5cb29f26596fa9169c6a9b0309d9d0ecbb515706251ff473f4ac98f7b41be7d89c089ce3b8537ade54

data/.rubocop.yml

@@ -0,0 +1,23 @@
+AllCops:
+  NewCops: enable
+  Exclude:
+    - 'spec/fixtures/**/*'
+    - 'tmp/**/*'
+    - '.git/**/*'
+    - 'bin/*'
+Style/ClassAndModuleChildren:
+  Exclude: 
+    - 'spec/**/*'
+Metrics/BlockLength:
+  Exclude: 
+    - 'spec/**/*'
+    - '*.gemspec'
+Metrics/MethodLength:
+  Enabled: false
+Lint/ConstantDefinitionInBlock:
+  Exclude: 
+    - 'spec/**/*'
+Style/Documentation:
+  Enabled: false
+Style/StringLiterals:
+  EnforcedStyle: double_quotes

data/.ruby-version

@@ -0,0 +1 @@
+3.1.4

data/Appraisals

@@ -0,0 +1,21 @@
+appraise "railties-7-sidekiq" do
+  gem "railties", "7"
+  gem "sidekiq", "7"
+end
+
+appraise "railties-7-no-sidekiq" do
+  gem "railties", "7"
+end
+
+appraise "railties-6-sidekiq" do
+  gem "railties", "6"
+  gem "sidekiq", "7"
+end
+
+appraise "railties-6-no-sidekiq" do
+  gem "railties", "6"
+end
+
+appraise "no-railties-no-sidekiq" do
+  # nothing extra
+end

data/CHANGELOG.md

@@ -1,5 +1,22 @@
 ## [Unreleased]
 
-## [0.1.0] - 2023-12-16
+## [0.1.0-alpha.1] - 2023-12-16
 
 - Initial release
+
+## [0.2.0-alpha.1] - 2023-12-27
+
+- Added support for Interactify.promising syntax in organizers
+
+## [0.3.0-alpha.1] - 2023-12-29
+
+- Added support for `{if: :condition, then: A, else: B}` in organizers
+
+## [0.3.0-alpha.2] - 2023-12-29
+
+- Remove deep_matching development dependency
+
+## [0.3.0-RC1] - 2023-12-29
+
+- Fixed to work with and make optional dependencies for sidekiq and railties. Confirmed as working with ruby >= 3.1.4
+

data/README.md

@@ -1,11 +1,59 @@
 # Interactify
 
-Interactors are a great way to encapsulate business logic in a Rails application. 
-However, sometimes in complex interactor chains, the complex debugging happens at one level up from your easy to read and test interactors.
+[![Gem Version](https://badge.fury.io/rb/interactify.svg)](https://badge.fury.io/rb/interactify)
+![Dependabot Status](https://api.dependabot.com/badges/status?host=github&repo=markburns/interactify)
+[![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
+![Ruby 3.3.0](https://img.shields.io/badge/ruby-3.3.0-green.svg)
+![Ruby 3.2.2](https://img.shields.io/badge/ruby-3.2.2-green.svg)
+![Ruby 3.1.4](https://img.shields.io/badge/ruby-3.1.4-green.svg)
+[![Code Climate](https://codeclimate.com/github/markburns/interactify/badges/gpa.svg)](https://codeclimate.com/github/markburns/interactify)
+
+Interactify enhances Rails applications by simplifying complex interactor chains. 
+This gem builds on [interactors](https://github.com/collectiveidea/interactor) and [interactor-contracts](https://github.com/michaelherold/interactor-contracts) to improve readability and maintainability of business logic. 
+We depend on activesupport, and optionally on railties and sidekiq. So it's a good fit for Rails projects using Sidekiq, offering advanced features for chain management and debugging. 
+Interactify is about making interactor usage in Rails more efficient and less error-prone, reducing the overhead of traditional interactor orchestration.
 
-Interactify wraps the interactor and interactor-contract gem and provides additional functionality making chaining and understanding interactor chains easier.
+## Installation
+
+```ruby
+gem 'interactify'
+```
+
+## Usage
+
+### Initializer
+
+```ruby
+# in config/initializers/interactify.rb
+Interactify.configure do |config|
+  # default
+  # config.root = Rails.root / 'app'
+end
+
+Interactify.on_contract_breach do |context, attrs|
+  # maybe add context to Sentry or Honeybadger etc here
+end
+
+Interactify.before_raise do |exception|
+  # maybe add context to Sentry or Honeybadger etc here
+end
+```
+
+### Using the RSpec matchers
+```ruby
+# e.g. in spec/supoort/interactify.rb
+require 'interactify/rspec/matchers'
+
+expect(described_class).to expect_inputs(:foo, :bar, :baz)
+expect(described_class).to promise_outputs(:fee, :fi, :fo, :fum)
+```
 
 ### Syntactic Sugar
+- Everything is an Organizer/Interactor and supports interactor-contracts.
+- They only becomes considered an organizer once `organize` is called.
+- They could technically be both (if you want?) but you have to remember to call `super` within `call` to trigger the organized interactors.
+- Concise syntax for most common scenarios with `expects` and `promises`. Verifying the presence of the keys/values.
+- Automatic delegation of expected and promised keys to the context.
 
 ```ruby
 # before
@@ -16,13 +64,14 @@ class LoadOrder
 
   expects do
     required(:id).filled
+    required(:something_else).filled
+    required(:a_boolean_flag)
   end
 
   promises do
     required(:order).filled
   end
 
-
   def call
     context.order = Order.find(context.id)
   end
@@ -35,7 +84,8 @@ end
 class LoadOrder
   include Interactify
 
-  expect :id
+  expect :id, :something_else
+  expect :a_boolean_flag, filled: false
   promise :order
 
   def call
@@ -47,8 +97,8 @@ end
 
 ### Lambdas
 
-With vanilla interactors, it's not possible to use lambdas in organizers, and sometimes we only want a lambda.
-So we added support.
+With vanilla interactors, it wasn't possible to use lambdas in organizers.
+But sometimes we only want a lambda. So we added support.
 
 ```ruby
 organize LoadOrder, ->(context) { context.order = context.order.decorate }
@@ -63,7 +113,7 @@ organize \
 
 Sometimes we want an interactor for each item in a collection.
 But it gets unwieldy. 
-It was complex procedural code and is now broken into neat SRP classes (Single Responsibility Principle). 
+It was complex procedural code and is now broken into neat [SRP classes](https://en.wikipedia.org/wiki/Single_responsibility_principle). 
 But there is still boilerplate and jumping around between files to follow the orchestration.
 It's easy to get lost in the orchestration code that occurs across say 7 or 8 files.
 
@@ -115,7 +165,6 @@ class DoSomethingWithOrder
 end
 ```
 
-
 ```ruby
 # after
 class OuterOrganizer
@@ -136,7 +185,6 @@ class LoadOrder
   end
 end
 
-
 class DoSomethingWithOrder
   # ... boilerplate ...
   def call
@@ -145,7 +193,7 @@ class DoSomethingWithOrder
 end
 ```
 
-### Conditionals (if/else)
+### Conditionals (if/else) with lambda
 
 Along the same lines of each/iteration. We sometimes have to 'break the chain' with interactors just to conditionally call one interactor chain path or another.
 
@@ -170,26 +218,22 @@ class InnerThing
 end
 ```
 
-
 ```ruby
 # after
 class OuterThing
   # ... boilerplate ...
   organize \
     SetupStep,
-    self.if(->(c){ c.thing == 'a' }, DoThingA, DoThingB),
-end
 
-```
+    # lambda conditional
+    self.if(->(c){ c.thing == 'a' }, DoThingA, DoThingB),
 
-### More Conditionals 
+    # context conditional
+    self.if(:some_key_on_context, DoThingA, DoThingB),
 
-```ruby
-class OuterThing
-  # ... boilerplate ...
-  organize \
-    self.if(:key_set_on_context, DoThingA, DoThingB),
-    AfterBothCases
+    # alternative hash syntax
+    {if: :key_set_on_context, then: DoThingA, else: DoThingB},
+    AfterDoThis
 end
 ```
 
@@ -210,49 +254,120 @@ end
 
 ```
 
-### Sidekiq Jobs
-Sometimes you want to asyncify an interactor.
+### Contract validation failures
+Sometimes contract validation fails at runtime as an exception. It's something unexpected and you'll have an `Interactor::Failure` sent to rollbar/sentry/honeybadger.
+If the context is large it's often hard to spot what the actual problem is or where it occurred.
+
+#### before 
+```
+Interactor::Failure
+
+#<Interactor::Context output_destination="DataExportSystem", output_format=:xml, region_code="XX", custom_flag=false, process_mode="sample", cache_identifier="GenericProcessorSample-XML-XX-0", data_key="GenericProcessorSample", data_version=0, last_process_time=2023-12-26 04:00:18.953000000 GMT +00:00, process_start_time=2023-12-26 06:45:17.915237484 UTC, updated_ids=[BSON::ObjectId('123f77a58444201ff1f0611a'), BSON::ObjectId('123f78148444201fd62a2e9b'), BSON::ObjectId('12375d8084442038712ba40e')], lock_info=#<Processing::Lock _id: 123a767d7b944674cc069064, created_at: 2023-12-26 06:45:17.992417809 UTC, updated_at: 2023-12-26 06:45:17.992417809 UTC, processor: "DataExportSystem", format: "xml", type: "sample">, expired_cache_ids=[], jobs=['jobs must be filled'] items=#<Mongoid::Criteria (Interactor::Failure)
+, tasks=[]>
+```
+
+#### after with call 
+```
+#<Interactor::Context output_destination="DataExportSystem", output_format=:xml, region_code="XX", custom_flag=false, process_mode="sample", cache_identifier="GenericProcessorSample-XML-XX-0", data_key="GenericProcessorSample", data_version=0, last_process_time=2023-12-26 04:00:18.953000000 GMT +00:00, process_start_time=2023-12-26 06:45:17.915237484 UTC, updated_ids=[BSON::ObjectId('123f77a58444201ff1f0611a'), BSON::ObjectId('123f78148444201fd62a2e9b'), BSON::ObjectId('12375d8084442038712ba40e')], lock_info=#<Processing::Lock _id: 123a767d7b944674cc069064, created_at: 2023-12-26 06:45:17.992417809 UTC, updated_at: 2023-12-26 06:45:17.992417809 UTC, processor: "DataExportSystem", format: "xml", type: "sample">, expired_cache_ids=[], tasks=['tasks must be filled'] items=#<Mongoid::Criteria (Interactor::Failure)
+, tasks=[], contract_failures={:tasks=>["tasks must be filled"]}>
+```
+
+#### after with call!
+```
+#<SomeSpecificInteractor::ContractFailure output_destination="DataExportSystem", output_format=:xml, region_code="XX", custom_flag=false, process_mode="sample", cache_identifier="GenericProcessorSample-XML-XX-0", data_key="GenericProcessorSample", data_version=0, last_process_time=2023-12-26 04:00:18.953000000 GMT +00:00, process_start_time=2023-12-26 06:45:17.915237484 UTC, updated_ids=[BSON::ObjectId('123f77a58444201ff1f0611a'), BSON::ObjectId('123f78148444201fd62a2e9b'), BSON::ObjectId('12375d8084442038712ba40e')], lock_info=#<Processing::Lock _id: 123a767d7b944674cc069064, created_at: 2023-12-26 06:45:17.992417809 UTC, updated_at: 2023-12-26 06:45:17.992417809 UTC, processor: "DataExportSystem", format: "xml", type: "sample">, expired_cache_ids=[], tasks=['tasks must be filled'] items=#<Mongoid::Criteria (Interactor::Failure)
+, tasks=[], contract_failures={:tasks=>["tasks must be filled"]}>
+```
+
+### Promising
+You can annotate your interactors in the organize arguments with their promises.
+This then acts as executable documentation that is validated at load time and enforced to stay in sync with the interactor.
+
+A writer of an organizer may quite reasonably expect `LoadOrder` to promise `:order`, but for the reader, it's not always as immediately obvious
+which interactor in the chain is responsible for provides which key.
 
 ```ruby
-# before
-class SomeInteractor
-  include Interactify
+organize \
+  LoadOrder.promising(:order), 
+  TakePayment.promising(:payment_transaction)
+```
 
-  def call
-    # ...
-  end
-end
+This will be validated at load time against the interactors promises.
+An example of a failure would be:
+
+```
+SomeOrganizer::DoStep1 does not promise:
+step_1
+
+Actual promises are:
+step1
+```
+
+### Interactor wiring specs
+Sometimes you have an interactor chain that fails because something is expected deeper down the chain and not provided further up the chain. 
+The existing way to solve this is with enough integration specs to catch them, hunting and sticking a `byebug`, `debugger` or `binding.pry` in at suspected locations and inferring where in the chain the wiring went awry.
+
+But we can do better than that if we always `promise` something that is later `expect`ed.
+
+In order to detect these wiring issues, stick a spec in your test suite like this:
 
-clsas SomeInteractorJob
-  include Sidekiq::Job
+```ruby
+RSpec.describe 'InteractorWiring' do
+  it 'validates the interactors in the whole app', :aggregate_failures do
+    errors = Interactify.validate_app(ignore: [/Priam/])
 
-  def perform(*args)
-    SomeInteractor.call(*args)
+    expect(errors).to eq ''
   end
 end
+```
 
-SomeInteractor.call(*args)
-code is changed to
-SomeInteractorJob.perform_async(*args)
 ```
+    Missing keys: :order_id
+              in: AssignOrderToUser
+             for: PlaceOrder
+```
+
+This allows you to quickly see exactly where you missed assigning something to the context.
+Combine with lambda debugging `->(ctx) { byebug if ctx.order_id.nil?},` in your chains to drop into the exact
+location in the chain to find where to make the change.
+
+### RSpec matchers
+Easily add [low value, low cost](https://noelrappin.com/blog/2017/02/high-cost-tests-and-high-value-tests/) specs for your expects and promises.
 
 ```ruby
-# after
-class SomeInteractor
-  include Interactify
+expect(described_class).to expect_inputs(:order_id)
+expect(described_class).to promise_outputs(:order)
+```
 
-  def call
-    # ...
-  end
-end
+### Sidekiq Jobs
+Sometimes you want to asyncify an interactor.
 
-# no need to manually create a job class or handle the perform/call impedance mismatch
-SomeInteractor::Async.call(*args)
+#### before
+```diff
+- SomeInteractor.call(*args)
++ class SomeInteractorJob
++   include Sidekiq::Job
++
++   def perform(*args)
++     SomeInteractor.call(*args)
++   end
++ end
++
++ SomeInteractorJob.perform_async(*args)
+```
 
-# This also makes it easy to add cron jobs to run interactors. As any interactor can be asyncified.
-# By using it's internal Async class.
+#### after
+```diff
+- SomeInteractor.call!(*args)
++ SomeInteractor::Async.call!(*args)
 ```
 
+No need to manually create a job class or handle the perform/call impedance mismatch
+
+This also makes it easy to add cron jobs to run interactors. As any interactor can be asyncified.
+By using it's internal Async class.
+
+N.B. as your class is now executing asynchronously you can no longer rely on its promises later on in the chain.
+
 ## FAQs
 - This is ugly isn't it?
 
@@ -268,96 +383,33 @@ class OuterOrganizer
     )
 end
 ```
+1. Do you find the syntax of OuterOrganizer ugly?
 
-Yes I agree. It's early days and I'm open to syntax improvement ideas. This is really about it being conceptually less ugly than the alternative, which is to jump around between lots of files. In the existing alternative to using this gem the ugliness is not within each individual file, but within the overall hidden architecture and the hunting process of jumping around in complex interactor chains. We can't see that ugliness but we probably experience it. If you don't feel or experience that ugliness then this gem may not be the right fit for you.
-
-
-- Is this interactor/interactor-contracts compatible? 
-Yes and we use them as dependencies. It's possible we'd drop those dependencies in the future but unlikely. I think it's highly likely we'd retain compatibility.
+While the syntax might seem unconventional initially, its conceptual elegance lies in streamlining complex interactor chains. Traditional methods often involve navigating through multiple files, creating a hidden and cumbersome architecture. This gem aims to alleviate that by centralizing operations, making the overall process more intuitive.
 
+2. Is this compatible with interactor/interactor-contracts?
 
-- Why not propose changes to the interactor or interactor-contracts gem?
-Honestly, I think both are great and why we've built on top of them. 
-I presume they'd object to such an extensive opinionated change, and I think that would be the right decision too.
-If this becomes more stable, less coupled to Rails, there's interest, and things we can provide upstream I'd be happy to propose changes to those gems.
+Yes, it's fully compatible. We currently use these as dependencies. While there's a possibility of future changes, maintaining this compatibility is a priority.
 
-- Isn't this all just syntactic sugar?
-Yes, but it's sugar that makes the code easier to read and understand.
+3. Why not suggest enhancements to the interactor or interactor-contracts gems?
 
-- Is it really easier to parse this new DSL/syntax than POROs?
-That's subjective, but I think so. The benefit is you have fewer extraneous files patching over a common problem in interactors.
+These gems are excellent in their own right, which is why we've built upon them. Proposing such extensive changes might not align with their current philosophy. However, if our approach proves stable and garners interest, we're open to discussing potential contributions to these gems.
 
-- But it gets really verbose and complex!
-Again this is subjective, but if you've worked with apps with hundred or thousands of interactors, you'll have encountered these problems.
-I think when we work with interactors we're in one of two modes. 
-Hunting to find the interactor we need to change, or working on the interactor we need to change.
-This makes the first step much easier. 
-The second step has always been a great experience with interactors.
+4. Is this just syntactic sugar?
 
-- I prefer Service Objects
-If you're not heavily invested into interactors this may not be for you.
-I love the chaining interactors provide. 
-I love the contracts. 
-I love the simplicity of the interface.
-I love the way they can be composed. 
-I love the way they can be tested.
-When I've used service objects, I've found them to be more complex to test and compose.
-I can't see a clean way that using service objects to compose interactors could work well without losing some of the aforementioned benefits.
-
-### TODO
-We want to add support for explicitly specifying promises in organizers. The benefit here is on clarifying the contract between organizers and interactors.
-A writer of an organizer may expect LoadOrder to promise :order, but for the reader, it's not quite as explicit.
-The expected syntax will be
-
-```ruby
-organize \
-  LoadOrder.promising(:order), 
-  TakePayment.promising(:payment_transaction)
-```
-
-This will be validated at test time against the interactors promises.
-
-## Installation
-
-TODO: Replace `UPDATE_WITH_YOUR_GEM_NAME_PRIOR_TO_RELEASE_TO_RUBYGEMS_ORG` with your gem name right after releasing it to RubyGems.org. Please do not do it earlier due to security reasons. Alternatively, replace this section with instructions to install your gem from git if you don't plan to release to RubyGems.org.
-
-Install the gem and add to the application's Gemfile by executing:
-
-    $ bundle add UPDATE_WITH_YOUR_GEM_NAME_PRIOR_TO_RELEASE_TO_RUBYGEMS_ORG
-
-If bundler is not being used to manage dependencies, install the gem by executing:
-
-    $ gem install UPDATE_WITH_YOUR_GEM_NAME_PRIOR_TO_RELEASE_TO_RUBYGEMS_ORG
-
-## Usage
-
-```ruby
-# e.g. in spec/supoort/interactify.rb
-require 'interactify/rspec/matchers'
-
-Interactify.configure do |config|
-  config.root = Rails.root '/app'
-end
-
-Interactify.on_contract_breach do |context, attrs|
-  # maybe add context to Sentry or Honeybadger etc here
-end
-
-Interactify.before_raise do |exception|
-  # maybe add context to Sentry or Honeybadger etc here
-end
-```
+It's more than that. This approach enhances readability and comprehension of the code. It simplifies the structure, making it easier to navigate and maintain.
 
-## Development
+5. Is the new DSL/syntax easier to understand than plain old Ruby objects (POROs)?
 
-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.
+This is subjective, but we believe it is. It reduces the need for numerous files addressing common interactor issues, thereby streamlining the workflow.
 
-To install this gem onto 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 the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+6. Doesn't this approach become verbose and complex in large applications?
 
-## Contributing
+While it may appear so, this method shines in large-scale applications with numerous interactors. It simplifies locating and modifying the necessary interactors, which is often a cumbersome process.
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/interactify.
+7. What if I prefer using Service Objects?
 
+That's completely valid. Service Objects have their merits, but this gem is particularly useful for those deeply engaged with interactors. It capitalizes on the chaining, contracts, simplicity, composability, and testability that interactors offer. Combining Service Objects with interactors might not retain these advantages as effectively.
 ## License
 
 The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).

data/gemfiles/.bundle/config

@@ -0,0 +1,2 @@
+---
+BUNDLE_RETRY: "1"

data/gemfiles/no_railties_no_sidekiq.gemfile

@@ -0,0 +1,16 @@
+# This file was generated by Appraisal
+
+source "https://rubygems.org"
+
+gem "rake", "~> 13.0"
+
+group :development do
+  gem "bundler", "~> 2.0"
+end
+
+group :test do
+  gem "simplecov", require: false
+  gem "rspec", "~> 3.0"
+end
+
+gemspec path: "../"

data/gemfiles/no_railties_no_sidekiq.gemfile.lock

@@ -0,0 +1,127 @@
+PATH
+  remote: ..
+  specs:
+    interactify (0.3.0.pre.alpha.2)
+      activesupport (>= 6.0.0)
+      interactor
+      interactor-contracts
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activesupport (7.1.2)
+      base64
+      bigdecimal
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      connection_pool (>= 2.2.5)
+      drb
+      i18n (>= 1.6, < 2)
+      minitest (>= 5.1)
+      mutex_m
+      tzinfo (~> 2.0)
+    appraisal (2.5.0)
+      bundler
+      rake
+      thor (>= 0.14.0)
+    base64 (0.2.0)
+    bigdecimal (3.1.5)
+    concurrent-ruby (1.2.2)
+    connection_pool (2.4.1)
+    debug (1.9.1)
+      irb (~> 1.10)
+      reline (>= 0.3.8)
+    diff-lcs (1.5.0)
+    docile (1.4.0)
+    drb (2.2.0)
+      ruby2_keywords
+    dry-configurable (1.0.1)
+      dry-core (~> 1.0, < 2)
+      zeitwerk (~> 2.6)
+    dry-core (1.0.0)
+      concurrent-ruby (~> 1.0)
+      zeitwerk (~> 2.6)
+    dry-inflector (1.0.0)
+    dry-initializer (3.1.1)
+    dry-logic (1.5.0)
+      concurrent-ruby (~> 1.0)
+      dry-core (~> 1.0, < 2)
+      zeitwerk (~> 2.6)
+    dry-schema (1.13.3)
+      concurrent-ruby (~> 1.0)
+      dry-configurable (~> 1.0, >= 1.0.1)
+      dry-core (~> 1.0, < 2)
+      dry-initializer (~> 3.0)
+      dry-logic (>= 1.4, < 2)
+      dry-types (>= 1.7, < 2)
+      zeitwerk (~> 2.6)
+    dry-types (1.7.1)
+      concurrent-ruby (~> 1.0)
+      dry-core (~> 1.0)
+      dry-inflector (~> 1.0)
+      dry-logic (~> 1.4)
+      zeitwerk (~> 2.6)
+    dry-validation (1.10.0)
+      concurrent-ruby (~> 1.0)
+      dry-core (~> 1.0, < 2)
+      dry-initializer (~> 3.0)
+      dry-schema (>= 1.12, < 2)
+      zeitwerk (~> 2.6)
+    i18n (1.14.1)
+      concurrent-ruby (~> 1.0)
+    interactor (3.1.2)
+    interactor-contracts (0.3.0)
+      dry-validation (~> 1.0)
+      interactor (~> 3)
+    io-console (0.7.1)
+    irb (1.11.0)
+      rdoc
+      reline (>= 0.3.8)
+    minitest (5.20.0)
+    mutex_m (0.2.0)
+    psych (5.1.2)
+      stringio
+    rake (13.1.0)
+    rdoc (6.6.2)
+      psych (>= 4.0.0)
+    reline (0.4.1)
+      io-console (~> 0.5)
+    rspec (3.12.0)
+      rspec-core (~> 3.12.0)
+      rspec-expectations (~> 3.12.0)
+      rspec-mocks (~> 3.12.0)
+    rspec-core (3.12.2)
+      rspec-support (~> 3.12.0)
+    rspec-expectations (3.12.3)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.12.0)
+    rspec-mocks (3.12.6)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.12.0)
+    rspec-support (3.12.1)
+    ruby2_keywords (0.0.5)
+    simplecov (0.22.0)
+      docile (~> 1.1)
+      simplecov-html (~> 0.11)
+      simplecov_json_formatter (~> 0.1)
+    simplecov-html (0.12.3)
+    simplecov_json_formatter (0.1.4)
+    stringio (3.1.0)
+    thor (1.3.0)
+    tzinfo (2.0.6)
+      concurrent-ruby (~> 1.0)
+    zeitwerk (2.6.12)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  appraisal
+  bundler (~> 2.0)
+  debug
+  interactify!
+  rake (~> 13.0)
+  rspec (~> 3.0)
+  simplecov
+
+BUNDLED WITH
+   2.4.22

data/gemfiles/railties_6.gemfile

@@ -0,0 +1,14 @@
+# This file was generated by Appraisal
+
+source "https://rubygems.org"
+
+gem "simplecov", require: false
+gem "rake", "~> 13.0"
+gem "railties", "6"
+gem "sidekiq", "7"
+
+group :test do
+  gem "rspec", "~> 3.0"
+end
+
+gemspec path: "../"