uses 1.0.0.pre.beta1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 88067fa2445e42cb0c82777e973ea4f99e8875d5aa9b5e57f2cf6e5c41bf7fdd
+  data.tar.gz: 8c81ad281c316cc68f09f9d6f24fc4df3b7f9871fc0db567326a3bafa3d3efc5
+SHA512:
+  metadata.gz: 3aa03891e384844990ffeb3ae2e1d1763bcd0ed4debfe169427d07814ea88339cbd9dbaa8aa6c9690de13a1c2796fb4d7a1063b47c289cc552e6e376b3ef0f90
+  data.tar.gz: 613162f4b7710cb491bffccdd5eef58a0895c5e96e36e8fe4132c4454e10a96cbfc6f78144563f2ea449e23c1a9952cf9cb0b3fc34470b7ac12027dd6d90d07c

data/.circleci/config.yml

@@ -0,0 +1,35 @@
+version: 2.1
+orbs:
+  # See https://circleci.com/developer/orbs/orb/circleci/ruby
+  ruby: circleci/ruby@1.2.0
+jobs:                # keyword
+  test:              # my name for the job
+    parameters:      # keyword
+      ruby-version:  # my parameter name
+        type: string # type is a keyword
+    docker:          # keyword
+      - image: cimg/base:stable
+    steps:                                       # keyword
+      - checkout                                 # magic name
+      - ruby/install:                            # ruby/ is from the orb name, install is a command in that orb
+          version: << parameters.ruby-version >> # magic nonsense for param subst
+      - run:
+          command: "bin/setup"
+      - run:
+          name: "Create the test results directory because you can't just store_test_results with a file and if you do you do not get any sort of error because wtf is with this platform?"
+          command: mkdir -p /tmp/test-results
+      - run:
+          command: bin/ci /tmp/test-results/rspec_results.xml
+      - store_test_results:                      # store_test_results is magic from circle
+          path: /tmp/test-results                # path is a param to store_test_results and it must be a directory not a file
+      - store_artifacts:                         # store_artifacts is magic from circle
+          path: /tmp/test-results                # path is the param to store_artifacts
+workflows:              # keyword
+  all-rubies:           # my name for the workflow
+    jobs:               # keyword
+      - test:           # my name for the job
+          matrix:       # keyword
+            parameters: # keyword
+              # All rubies being maintained per this page:
+              # https://www.ruby-lang.org/en/downloads/branches/
+              ruby-version: [ "2.5", "2.6", "2.7", "3.0" ]

data/.gitignore

@@ -0,0 +1,9 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+Gemfile.lock

data/.rspec

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

data/.ruby-version

@@ -0,0 +1 @@
+3.0.2

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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, 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 davetron5000 (at) gmail.com. 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+

data/CONTRIBUTING.md

@@ -0,0 +1,5 @@
+# Contributing
+
+* Code changes for style, cleanliness, eleganance, or other aesthetic stuff will not be accepted.
+* All proposed changes must have a clear problem statement and be based on a real-world scenario. Imagined problems will not be solved.
+* Tests are appreciated with all pull requests.

data/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in with_clues.gemspec
+gemspec
+
+gem "rake", "~> 12.0"

data/LICENSE.md

@@ -0,0 +1,33 @@
+[uses] Copyright (2021) (David Copeland)(“Licensor”)
+
+Hippocratic License Version Number: 2.1.
+
+Purpose. The purpose of this License is for the Licensor named above to permit the Licensee (as defined below) broad permission, if consistent with Human Rights Laws and Human Rights Principles (as each is defined below), to use and work with the Software (as defined below) within the full scope of Licensor’s copyright and patent rights, if any, in the Software, while ensuring attribution and protecting the Licensor from liability.
+
+Permission and Conditions. The Licensor grants permission by this license (“License”), free of charge, to the extent of Licensor’s rights under applicable copyright and patent law, to any person or entity (the “Licensee”) obtaining a copy of this software and associated documentation files (the “Software”), to do everything with the Software that would otherwise infringe (i) the Licensor’s copyright in the Software or (ii) any patent claims to the Software that the Licensor can license or becomes able to license, subject to all of the following terms and conditions:
+
+* Acceptance. This License is automatically offered to every person and entity subject to its terms and conditions. Licensee accepts this License and agrees to its terms and conditions by taking any action with the Software that, absent this License, would infringe any intellectual property right held by Licensor.
+
+* Notice. Licensee must ensure that everyone who gets a copy of any part of this Software from Licensee, with or without changes, also receives the License and the above copyright notice (and if included by the Licensor, patent, trademark and attribution notice). Licensee must cause any modified versions of the Software to carry prominent notices stating that Licensee changed the Software. For clarity, although Licensee is free to create modifications of the Software and distribute only the modified portion created by Licensee with additional or different terms, the portion of the Software not modified must be distributed pursuant to this License. If anyone notifies Licensee in writing that Licensee has not complied with this Notice section, Licensee can keep this License by taking all practical steps to comply within 30 days after the notice. If Licensee does not do so, Licensee’s License (and all rights licensed hereunder) shall end immediately.
+
+* Compliance with Human Rights Principles and Human Rights Laws.
+
+    1. Human Rights Principles.
+
+        (a) Licensee is advised to consult the articles of the United Nations Universal Declaration of Human Rights and the United Nations Global Compact that define recognized principles of international human rights (the “Human Rights Principles”). Licensee shall use the Software in a manner consistent with Human Rights Principles.
+
+        (b) Unless the Licensor and Licensee agree otherwise, any dispute, controversy, or claim arising out of or relating to (i) Section 1(a) regarding Human Rights Principles, including the breach of Section 1(a), termination of this License for breach of the Human Rights Principles, or invalidity of Section 1(a) or (ii) a determination of whether any Law is consistent or in conflict with Human Rights Principles pursuant to Section 2, below, shall be settled by arbitration in accordance with the Hague Rules on Business and Human Rights Arbitration (the “Rules”); provided, however, that Licensee may elect not to participate in such arbitration, in which event this License (and all rights licensed hereunder) shall end immediately. The number of arbitrators shall be one unless the Rules require otherwise.
+
+        Unless both the Licensor and Licensee agree to the contrary: (1) All documents and information concerning the arbitration shall be public and may be disclosed by any party; (2) The repository referred to under Article 43 of the Rules shall make available to the public in a timely manner all documents concerning the arbitration which are communicated to it, including all submissions of the parties, all evidence admitted into the record of the proceedings, all transcripts or other recordings of hearings and all orders, decisions and awards of the arbitral tribunal, subject only to the arbitral tribunal's powers to take such measures as may be necessary to safeguard the integrity of the arbitral process pursuant to Articles 18, 33, 41 and 42 of the Rules; and (3) Article 26(6) of the Rules shall not apply.
+
+    2. Human Rights Laws. The Software shall not be used by any person or entity for any systems, activities, or other uses that violate any Human Rights Laws.  “Human Rights Laws” means any applicable laws, regulations, or rules (collectively, “Laws”) that protect human, civil, labor, privacy, political, environmental, security, economic, due process, or similar rights; provided, however, that such Laws are consistent and not in conflict with Human Rights Principles (a dispute over the consistency or a conflict between Laws and Human Rights Principles shall be determined by arbitration as stated above).  Where the Human Rights Laws of more than one jurisdiction are applicable or in conflict with respect to the use of the Software, the Human Rights Laws that are most protective of the individuals or groups harmed shall apply.
+
+    3. Indemnity. Licensee shall hold harmless and indemnify Licensor (and any other contributor) against all losses, damages, liabilities, deficiencies, claims, actions, judgments, settlements, interest, awards, penalties, fines, costs, or expenses of whatever kind, including Licensor’s reasonable attorneys’ fees, arising out of or relating to Licensee’s use of the Software in violation of Human Rights Laws or Human Rights Principles.
+
+* Failure to Comply. Any failure of Licensee to act according to the terms and conditions of this License is both a breach of the License and an infringement of the intellectual property rights of the Licensor (subject to exceptions under Laws, e.g., fair use). In the event of a breach or infringement, the terms and conditions of this License may be enforced by Licensor under the Laws of any jurisdiction to which Licensee is subject. Licensee also agrees that the Licensor may enforce the terms and conditions of this License against Licensee through specific performance (or similar remedy under Laws) to the extent permitted by Laws. For clarity, except in the event of a breach of this License, infringement, or as otherwise stated in this License, Licensor may not terminate this License with Licensee.
+
+* Enforceability and Interpretation. If any term or provision of this License is determined to be invalid, illegal, or unenforceable by a court of competent jurisdiction, then such invalidity, illegality, or unenforceability shall not affect any other term or provision of this License or invalidate or render unenforceable such term or provision in any other jurisdiction; provided, however, subject to a court modification pursuant to the immediately following sentence, if any term or provision of this License pertaining to Human Rights Laws or Human Rights Principles is deemed invalid, illegal, or unenforceable against Licensee by a court of competent jurisdiction, all rights in the Software granted to Licensee shall be deemed null and void as between Licensor and Licensee. Upon a determination that any term or provision is invalid, illegal, or unenforceable, to the extent permitted by Laws, the court may modify this License to affect the original purpose that the Software be used in compliance with Human Rights Principles and Human Rights Laws as closely as possible. The language in this License shall be interpreted as to its fair meaning and not strictly for or against any party.
+
+* Disclaimer. TO THE FULL EXTENT ALLOWED BY LAW, THIS SOFTWARE COMES “AS IS,” WITHOUT ANY WARRANTY, EXPRESS OR IMPLIED, AND LICENSOR AND ANY OTHER CONTRIBUTOR SHALL NOT BE LIABLE TO ANYONE FOR ANY DAMAGES OR OTHER LIABILITY ARISING FROM, OUT OF, OR IN CONNECTION WITH THE SOFTWARE OR THIS LICENSE, UNDER ANY KIND OF LEGAL CLAIM.
+
+This Hippocratic License is an Ethical Source license (https://ethicalsource.dev) and is offered for use by licensors and licensees at their own risk, on an “AS IS” basis, and with no warranties express or implied, to the maximum extent permitted by Laws.

data/README.md

@@ -0,0 +1,368 @@
+# uses - declare dependencies between classes
+
+[![<sustainable-rails>](https://circleci.com/gh/sustainable-rails/uses.svg?style=shield)](https://app.circleci.com/pipelines/github/sustainable-rails/uses)
+
+Your *service layer* is a web of classes that depend on each other to get the job done. While you can manage that directly with code and test them
+directly using mocks or integration tests, declaring dependencies directly can reduce errors, increase consistency, and make your code a bit
+simpler.
+
+## Install
+
+Add to your `Gemfile`
+
+```ruby
+gem "uses"
+```
+
+## Usage
+
+Suppose you have a `PaymentsController` that uses a class called `PaymentProcessor`. Suppose that `PaymentProcessor` uses `Braintree::Gateway`
+under the covers:
+
+```
++--------------------+
+|                    |
+| PaymentsController |
+|                    |
++---+----------------+
+    |
+    |           +------------------+
+    \-«uses»--->|                  |
+                | PaymentProcessor |
+                |                  |
+                +------------------+
+                    |
+                    |           +--------------------+
+                    \-«uses»--->|                    |
+                                | Braintree::Gateway |
+                                |                    |
+                                +--------------------+
+```
+
+You might implement this like so:
+
+```ruby
+class PaymentsController < ApplicationController
+  def create
+    payment_processor.collect_payment(...)
+  end
+  
+private
+
+  def payment_processor
+    @payment_processor ||= PaymentProcessor.new
+  end
+end
+
+class PaymentProcessor
+  def collect_payment
+    braintree_gateway.sale(...)
+  end
+
+private
+
+  def braintree_gateway
+    @braintree_gateway ||= Braintree::Gateway.new
+  end
+end
+```
+
+This is fine, but with Uses you can declare these dependencies explicitly:
+
+```ruby
+class PaymentsController < ApplicationController
+  uses PaymentProcessor # <--------
+
+  def create
+    payment_processor.collect_payment(...)
+    #  ^
+    #  |
+    #  |
+    # Method dynamically defined when `uses` is called
+
+  end
+end
+
+class PaymentProcessor
+  uses Braintree::Gateway # <--------
+
+  def collect_payment
+    braintree_gateway.sale(...)
+    #  ^
+    #  |
+    #  |
+    # Method dynamically defined when `uses` is called
+  end
+end
+```
+
+## Why Would You Want This?
+
+By declaring dependencies like this, you:
+
+* save some code, which adds up as your application grows.
+* can detect circular dependencies, which is often a sign of trouble or confusion.
+* can ensure that if you mock a dependency, you class really does depend on it.
+* make dependants clear at the top of the class, but without adopting a complicated dependency-injection pattern.
+
+## Set Up
+
+Strictly speaking, to access `uses`, you should include `Uses::Method` into any class that needs it. Practically, this is what you should
+do:
+
+* Add it to `ApplicationController`:
+
+  ```ruby
+  class ApplicationController < ActionController::Base
+    include Uses::Method
+
+    # whatever else is in your ApplicationController
+  end
+  ```
+* Create `app/sevices/application_service.rb` like so:
+
+  ```ruby
+  class ApplicationService
+    include Uses::Method
+  end
+  ```
+
+  and have your service layer classes inherit from this
+* Add `Uses::Method` to any other base class where your service layer logic is initiated.
+
+## Testing Support
+
+You might test `PaymentProcessor` by mocking `Braintree::Gateway`, like so:
+
+```ruby
+RSpec.describe PaymentProcessor do
+  subject(:payment_processor) { described_class.new }
+
+  let(:braintree_gateway) { instance_double(Braintree::Gateway) }
+
+  before do
+    allow(Braintree::Gateway).to receive(:new).and_return(braintree_gateway)
+    allow(braintree_gateway).to receive(:sale)
+  end
+
+  describe "#collect_payment" do
+    it "calls braintree" do
+      payment_processor.collect_payment
+
+      expect(braintree_gateway).to have_received(:sale)
+    end
+  end
+end
+```
+
+When building out your service layer, having to repeatedly mock the call to `new` can be tedious.  If your class changes to need the class you are
+mocking, you don't have a good way to know that.  Instead, `inject_rspec_double` can solve both issues:
+
+```ruby
+RSpec.describe PaymentProcessor do
+  subject(:payment_processor) { described_class.new }
+
+  # vvvvvv
+  let(:braintree_gateway) { inject_rspec_double(payment_processor,Braintree::Gateway) }
+  # ^^^^^^
+
+  before do
+    # No need to mock :new
+    allow(braintree_gateway).to receive(:sale)
+  end
+
+  describe "#collect_payment" do
+    it "calls braintree" do
+      payment_processor.collect_payment
+
+      expect(braintree_gateway).to have_received(:sale)
+    end
+  end
+end
+```
+
+This saves a few lines of code (which, again, will add up over time), but will also fail is `PaymentProcessor` does not depend on
+`Braintree::Gateway` via `uses`.
+
+If you aren't using RSpec or want to control how the mock gets created, you can also use `inject_double`:
+
+```ruby
+RSpec.describe PaymentProcessor do
+  subject(:payment_processor) { described_class.new }
+
+  # vvvvvv
+  let(:braintree_gateway) { inject_double(payment_processor,Braintree::Gateway: double("BT Gateway")) }
+  # ^^^^^^
+
+  before do
+    # No need to mock :new
+    allow(braintree_gateway).to receive(:sale)
+  end
+
+  describe "#collect_payment" do
+    it "calls braintree" do
+      payment_processor.collect_payment
+
+      expect(braintree_gateway).to have_received(:sale)
+    end
+  end
+end
+```
+
+## Set Up for Testing
+
+You need to `require("uses/inject_double")` and then `include Uses::InjectDouble` to make `inject_rspec_double` and
+`inject_double` available. Practically speaking, you should do this in your base test case or RSpec configuration:
+
+```ruby
+# spec/spec_helper.rb
+require "uses/inject_double"
+
+RSpec.configure do |config|
+  config.include Uses::InjectDouble
+
+  # ... remainder of your configuration
+end
+```
+
+
+## Reference
+
+### `uses` macro
+
+The `uses` macro does two things:
+
+* Creates a private method that returns a memoized instance of the dependent class
+* Instantiates that class
+
+You can control both the name of the method and how the class is instantiated if needed, but the default behavior should work for most cases.
+
+The full signature of `uses` is:
+
+```ruby
+uses SomeClass, as: «method name», 
+                initialize: «initialization_strategy»
+```
+
+By default, the `«method name»` will be the underscorized version of the class, with slashes replaced by underscores, so for example `Braintree::Gateway` becomes `braintree_gateway`.
+
+By default `«initialization_strategy»` is `:new_no_args`, which instructs `uses` to simply call `new` without any args, e.g.
+`Braintree::Gateway.new`.
+
+Thus the method that gets defined would look like this:
+
+```ruby
+def braintree_gateway
+  @braintree_gateway ||= Braintree::Gateway.new
+end
+private :braintree_gateway
+```
+
+#### `as:` option
+
+By setting `as:` you can control the name of the private method if you don't like the default.  Generally, you should not do this, but it can be
+handy if you are migrating existing code to this gem and don't want to change variable names:
+
+```ruby
+uses Braintree::Gateway as: :braintree
+
+# creates this method:
+def braintree
+  @braintree ||= Braintree::Gateway.new
+end
+private :braintree
+```
+
+`as:` must be a value that can be used as a method in Ruby
+
+#### `initialize:` option
+
+Not all objects can be created with `.new`. Here are the possible values for `initialize:`
+
+* `:new_no_args` - This is the default and creates an instance by calling `new` without any args. This should be how most of the classes you create are initialized.
+* `:config_initializers` - This says that an instance has been pre-configured by a file in `config/initializers` that calls into Uses' configuration API like so:
+
+  ```ruby
+  # config/initializers/braintree.rb
+  Uses.initializers do |initializers|
+    initializers[Braintree::Gateway] = ->(*) {
+      Braintree::Gateway.new(
+        :environment => :sandbox,
+        :merchant_id => "your_merchant_id",
+        :public_key  => "your_public_key",
+        :private_key => "your_private_key",
+      )
+    }
+  end
+  ```
+
+  `initializers` is a hash that has the class as a key and a `Proc` as the value. That `Proc` will be used each time the class must be
+  instantiated.  This is the second preferred method for creating instances since it is desirable to have a single location for how an instance is
+  created if it must be created in a complex way.
+
+  Note that it doesn't have to be in a file in `config/initializers`, it just has to be loaded before any class that uses `uses` is loaded.
+* A `Proc` - If you set `initialize:` to a `Proc`, that `Proc` will be called to get the instance of the object.  This is useful if the way in which the object is created differs based on what class is including it. This should be used rarely.  Example:
+
+  ```ruby
+  class PaymentProcessor
+    uses Braintree::Gateway, initialize: ->(*) {
+      Braintree::Gateway.new(
+        :environment => :sandbox,
+        :merchant_id => "your_merchant_id",
+        :public_key  => "your_public_key",
+        :private_key => "your_private_key",
+      )
+    }
+  end
+  ```
+
+### `inject_rspec_double`
+
+The signature of this method is:
+
+```ruby
+inject_rspec_double(«object_with_dependency»,
+                    «class that it depends on»)
+```
+
+`inject_rspec_double` returns an instance created via RSpec's `instance_double` method.  It will raise an exception if `«object_with_dependency»`'s
+class does use call `uses «class that it depends on»`.  This way, if you refactor your class to no longer need this dependency, your test will
+fail.
+
+### `inject_double`
+
+The signature of this method is:
+
+```ruby
+inject_double(«object_with_dependency»,
+              «class that it depends on» => «mocked instance»)
+```
+
+This is useful if you need to control how the mocked instance is created or if you are not using RSpec.
+
+### `Uses.config`
+
+There is currently one configuration option.
+
+#### `:on_circular_dependency` option
+
+Because the proliferation of `uses` creates a structured representation of your service layer's dependencies, Uses can check for circular
+dependencies.  The reason this is important is that your code's behavior can become confusing if a dependency depends on another class that depends
+on it.
+
+By default, if a circular dependency is detected, Uses will emit a warning.  You can change this behavior by setting a config value,
+which you can do by creating `config/initializers/uses.rb`:
+
+```ruby
+# config/initializers/uses.rb
+Uses.config do |config|
+  config.on_circular_dependency = # one of :warn, :ignore, or :raise_error
+end
+```
+
+Valid values are:
+
+* `:warn` - this is the default and will emit a warning if a circular dependency is found.
+* `:ignore` - this will log a warning a debug level, effectively squelching the message. Don't use this unless you are migrating a service layer that has a lot of circular dependencies.
+* `:raise_error` - this will raise an `Uses::CircularDependency::Error` when it encounters a circular dependency.
+

data/Rakefile

@@ -0,0 +1,2 @@
+require "bundler/gem_tasks"
+task :default => :spec

data/bin/ci

@@ -0,0 +1,10 @@
+#!/bin/bash
+
+set -e
+echo "[bin/ci] Running tests"
+if [ -z $1 ]; then
+  bin/rspec --format=doc
+else
+  echo "[bin/ci] Generating JUnit XML output to $1"
+  bin/rspec --format RspecJunitFormatter --out $1 --format=doc
+fi

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "with_clues"
+
+# 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/rspec

@@ -0,0 +1,29 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+#
+# This file was generated by Bundler.
+#
+# The application 'rspec' is installed as part of a gem, and
+# this file is here to facilitate running it.
+#
+
+require "pathname"
+ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../../Gemfile",
+  Pathname.new(__FILE__).realpath)
+
+bundle_binstub = File.expand_path("../bundle", __FILE__)
+
+if File.file?(bundle_binstub)
+  if File.read(bundle_binstub, 300) =~ /This file was generated by Bundler/
+    load(bundle_binstub)
+  else
+    abort("Your `bin/bundle` was not generated by Bundler, so this binstub cannot run.
+Replace `bin/bundle` by running `bundle binstubs bundler --force`, then run this command again.")
+  end
+end
+
+require "rubygems"
+require "bundler/setup"
+
+load Gem.bin_path("rspec-core", "rspec")

data/bin/setup

@@ -0,0 +1,6 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle check || bundle install