rspec-should 0.1.0.beta1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: ff2296a5887f54941734e5b32da9a387ae38a4e4c5c501e35c56806ec2e7af11
+  data.tar.gz: 93cef85dd585866edc8e7a1b55f6eaf37032efb150373697dbf6610de341e7fd
+SHA512:
+  metadata.gz: 339630efb9b24f11de31741e0ad13d537973c20550a6ef2f10ed4a66620cba07d56020e38577ec5be7bf4967b5f671d27ce05df57419e97abe420537fdf4104f
+  data.tar.gz: 4c2cf5f78e955072f757d4064e473a6b1eaf4b6b3e554e1b63efa5373430096737b489f9520cfc3da703a190b38d1b23bffd35572a0091a01ade9afd33571d66

data/.github/workflows/ci.yml

@@ -0,0 +1,23 @@
+name: RSpec CI
+
+on:
+  push:
+    branches:
+      - 'main'
+      - '*-maintenance'
+  pull_request:
+    branches:
+      - '*'
+
+permissions:
+  contents: read
+
+jobs:
+  docs:
+    uses: ./.github/workflows/documentation_coverage.yml
+
+  rubocop:
+    uses: ./.github/workflows/rubocop.yml
+
+  specs:
+    uses: ./.github/workflows/rspec.yml

data/.github/workflows/documentation_coverage.yml

@@ -0,0 +1,21 @@
+name: Run Documentation Checks
+on: workflow_call
+
+permissions:
+  contents: read
+
+env:
+  RSPEC_CI: true
+
+jobs:
+  documentation_coverage:
+    name: Check documentation coverage for ${{ matrix.rspec_library }}
+    runs-on: 'ubuntu-latest'
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 4.0
+      - run: ./script/update_rubygems_and_install_bundler
+      - run: ./script/bundle
+      - run: ./script/check_documentation_coverage

data/.github/workflows/rspec.yml

@@ -0,0 +1,50 @@
+name: Run RSpec
+on:
+  workflow_call:
+
+permissions:
+  contents: read
+
+env:
+  RSPEC_CI: true
+
+jobs:
+  rspec:
+    name: Ruby ${{ matrix.ruby }}
+    runs-on: 'ubuntu-latest'
+    strategy:
+      matrix:
+        ruby:
+          - '4.0'
+          - '3.4'
+          - '3.3'
+          - '3.2'
+          - '3.1'
+          - '3.0'
+      fail-fast: false
+    continue-on-error: false
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+      - run: ./script/update_rubygems_and_install_bundler
+      - run: ./script/bundle
+      - run: ./bin/rspec
+
+  windows:
+    name: Ruby ${{ matrix.ruby }} (Windows)
+    runs-on: windows-latest
+    strategy:
+      matrix:
+        ruby:
+          - '3.4'
+      fail-fast: false
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          bundler-cache: true
+      - run: choco install ansicon
+      - run: bundle exec rspec --backtrace

data/.github/workflows/rubocop.yml

@@ -0,0 +1,19 @@
+name: Run Rubocop
+on:
+  workflow_call:
+
+permissions:
+  contents: read
+
+jobs:
+  rubocop:
+    name: Rubocop
+    runs-on: 'ubuntu-latest'
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 3.3
+      - run: script/update_rubygems_and_install_bundler
+      - run: script/bundle
+      - run: bin/rubocop

data/.yardopts

@@ -0,0 +1,7 @@
+--exclude features
+--no-private
+--markup markdown
+--default-return void
+-
+Changelog.md
+LICENSE.md

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,183 @@
+# Contributor Code of Conduct
+
+For the purpose of building a welcoming, harassment-free community that
+values contributions from anyone, the RSpec project has adopted the
+following code of conduct. All contributors and participants (including
+maintainers!) are expected to abide by its terms.
+
+As contributors and maintainers of this project, we pledge to make our community
+welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the
+dignity, rights, and contributions of all individuals, regardless of
+characteristics including race, ethnicity, caste, color, age, physical
+characteristics, neurodiversity, disability, sex or gender, gender identity
+or expression, sexual orientation, language, philosophy or religion, national
+or social origin, socio-economic position, level of education, or other status.
+The same privileges of participation are extended to everyone who participates
+in good faith and in accordance with this Covenant.
+
+By adopting this Code of Conduct, project maintainers commit themselves to
+fairly and consistently applying these principles to every aspect of managing
+this project. Project maintainers who do not follow or enforce the Code of
+Conduct may be permanently removed from the project team.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our
+community's expectations for positive behavior. We also understand that our
+words and actions may be interpreted differently than we intend based on
+culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each
+other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities,
+   and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the
+   **well-being of our community**.
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances,
+threats, and promotion of these behaviors are violations of this
+Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in
+   unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments
+   directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or
+   behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered
+   inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or
+   private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm
+   toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or
+   pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content
+   you contribute, including but not limited to the use of LLMs.
+3. **Promotional materials**. Sharing marketing or other commercial content in
+   a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which
+   includes, links or describes any other restricted behaviors.
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their
+best to collaborate. Not every conflict represents a code of conduct violation,
+and this Code of Conduct reinforces encouraged behaviors and norms that can
+help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly.
+
+To report a possible violation contact one of the project maintainers listed at
+https://rspec.info/about/. All complaints will be reviewed and investigated
+and will result in a response that is deemed necessary and appropriate to the
+circumstances.
+
+Maintainers take reports of violations seriously and will make every effort to
+respond in a timely manner. They will investigate all reports of code of conduct
+violations, reviewing messages, logs, and recordings, or interviewing witnesses
+and other participants. Maintainers will keep investigation and enforcement
+actions as transparent as possible while prioritizing safety and
+confidentiality. In order to honor these values, enforcement actions are carried
+out in private with the involved parties, but communicating to the whole
+community may be part of a mutually agreed upon resolution.
+
+## Addressing and Repairing Harm
+
+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.
+
+If an investigation that this Code of Conduct has been violated, the following
+enforcement ladder may be used to determine how best to repair harm, based on
+the incident's impact on the individuals involved and the community as a whole.
+Depending on the severity of a violation, lower rungs on the ladder may be
+skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning.
+   3) Repair: Examples of repair include a private written apology,
+      acknowledgement of responsibility, and seeking clarification on
+      expectations.
+
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a
+      warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown
+      period designed to underscore the seriousness of the situation and give
+      the community members involved time to process the incident. The cooldown
+      period may be limited to particular communication channels or interactions
+      with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the
+      cooldown period to reflect on actions and impact, and being thoughtful
+      about re-entering community spaces after the period is over.
+
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which have been issued warnings,
+      or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from
+      suspension. In general, temporary suspensions give the person being
+      suspended time to reflect upon their behavior and possible corrective
+      actions.
+   3) Repair: Examples of repair include respecting the spirit of the
+      suspension, meeting the specified conditions for return, and being
+      thoughtful about how to reintegrate with the community when the suspension
+      is lifted.
+
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps
+      on the ladder have failed to resolve, or a violation so serious that it
+      is determined there is no way to keep the community safe with this person
+      as a member.
+   2) Consequence: Access to all community spaces, tools, and communication
+      channels is removed. In general, permanent bans should be rarely used,
+      should have strong reasoning behind them, and should only be resorted to
+      if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the
+ability of maintainers to use their discretion and judgment, in keeping
+with the best interests of our community.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public or other
+spaces. Examples of representing our community include using an official email
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 3.0, available at
+[https://www.contributor-covenant.org/version/3/0/][version]
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and
+licensed under CC BY-SA 4.0. To view a copy of this license, visit
+[https://creativecommons.org/licenses/by-sa/4.0/][cc-by-sa]
+
+For answers to common questions about Contributor Covenant, see their
+[FAQ][faq].
+
+[cc-by-sa]: https://creativecommons.org/licenses/by-sa/4.0/
+[homepage]: https://contributor-covenant.org
+[faq]: https://www.contributor-covenant.org/faq
+[version]: https://www.contributor-covenant.org/version/3/0/

data/Changelog.md

@@ -0,0 +1,2 @@
+### Development
+[Full Changelog](https://github.com/rspec/rspec-should/compare/initial...main)

data/LICENSE.md

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2026 The RSpec Development Team
+
+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,41 @@
+# RSpec::Should
+
+This gem re-enables the `.should` syntax for RSpec gems (>= 4.0.0).
+
+Please note that the RSpec team does not recommend this gem, we instead recommend the `expect` syntax.
+
+## Why switch over from `should` to `expect`
+The `should` and `should_not` methods work by being added to every object. However, RSpec
+does not own every object and cannot ensure they work consistently on every object.
+In particular, they can lead to surprising failures when used with BasicObject-subclassed
+proxy objects.
+
+`expect` avoids these problems altogether by not needing to be available on all objects.
+
+## Installation
+
+Install the gem and add to the application's Gemfile by executing:
+
+```bash
+bundle add rspec-should
+```
+
+If bundler is not being used to manage dependencies, install the gem by executing:
+
+```bash
+gem install rspec-should
+```
+
+Then either require `rspec/should/enable` or manually call `RSpec::Should.enable!` at your desired time.
+
+## Usage
+
+See the documentation in RSpec::Should.
+
+## Contributing
+
+This gem is considered legacy support, whilst bug reports are welcome, there is no guarantee a member of
+the RSpec team will have time to attend to the issue. If you use this gem and encounter issues, please try
+to fix them yourself and submit a pull request.
+
+Contributors are expected to follow our [Code of Conduct](CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+require "rubocop/rake_task"
+
+RuboCop::RakeTask.new
+
+task default: %i[spec rubocop]

data/lib/rspec/should/enable.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+RSpec::Should.enable!

data/lib/rspec/should/version.rb

@@ -0,0 +1,11 @@
+# frozen_string_literal: true
+
+module RSpec
+  module Should
+    # Version information for RSpec Should.
+    module Version
+      # Current version of RSpec Should, in semantic versioning format.
+      STRING = "0.1.0.beta1"
+    end
+  end
+end

data/lib/rspec/should.rb

@@ -0,0 +1,168 @@
+# frozen_string_literal: true
+
+# Namespace for all RSpec code.
+module RSpec
+  # RSpec::Should provides the original  `should` and `should_not` syntax for RSpec >= 4.
+  #
+  # From the  beginning RSpec provided `should` and `should_not` methods
+  # to define expectations on any object. In version 2.11 `expect` method was
+  # introduced which became the recommended way to define expectations on an object.
+  #
+  # ### Why switch over from `should` to `expect`
+  #
+  # #### Fix edge case issues
+  #
+  # `should` and `should_not` work by being added to every object. However, RSpec
+  # does not own every object and cannot ensure they work consistently on every object.
+  # In particular, they can lead to surprising failures when used with BasicObject-subclassed
+  # proxy objects.
+  #
+  # `expect` avoids these problems altogether by not needing to be available on all objects.
+  #
+  # #### Unification of block and value syntaxes
+  #
+  # Before version 2.11 `expect` was just a more readable alternative for block
+  # expectations. Since version 2.11 `expect` can be used for both block and value
+  # expectations.
+  #
+  # ```ruby
+  # expect(actual).to eq(expected)
+  # expect { ... }.to raise_error(ErrorClass)
+  # ```
+  #
+  # See [http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax](http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax)
+  # For a detailed explanation
+  #
+  # ## Usage
+  # The `should` and `should_not` methods can be used to define expectations on any object.
+  #
+  # ```ruby
+  # actual.should eq expected
+  # actual.should be > 3
+  # [1, 2, 3].should_not include 4
+  # ```
+  #
+  # ## Using Built-in matchers
+  #
+  # ### Equivalence
+  # ```ruby
+  # actual.should     eq(expected)  # passes if actual == expected
+  # actual.should     == expected   # passes if actual == expected
+  # actual.should_not eql(expected) # passes if actual.eql?(expected)
+  # ```
+  #
+  # Note: we recommend the `eq` matcher over `==` to avoid Ruby's "== in a
+  # useless context" warning when the `==` matcher is used anywhere but the
+  # last statement of an example.
+  #
+  # ### Identity
+  #
+  # ```ruby
+  # actual.should     be(expected)    # passes if actual.equal?(expected)
+  # actual.should_not equal(expected) # passes if actual.equal?(expected)
+  # ```
+  #
+  # ### Comparisons
+  #
+  # ```ruby
+  # actual.should be >  expected
+  # actual.should be >= expected
+  # actual.should be <= expected
+  # actual.should be <  expected
+  # actual.should be_within(delta).of(expected)
+  # ```
+  #
+  # ### Regular expressions
+  #
+  # ```ruby
+  # actual.should match(/expression/)
+  # actual.should =~ /expression/
+  # ```
+  #
+  # ### Types/classes
+  #
+  # ```ruby
+  # actual.should     be_an_instance_of(expected)
+  # actual.should_not be_a_kind_of(expected)
+  # ```
+  #
+  # ### Truthiness
+  #
+  # ```ruby
+  # actual.should be_true  # passes if actual is truthy (not nil or false)
+  # actual.should be_false # passes if actual is falsy (nil or false)
+  # actual.should be_nil   # passes if actual is nil
+  # ```
+  #
+  # ### Predicate matchers
+  #
+  # ```ruby
+  # actual.should     be_xxx         # passes if actual.xxx?
+  # actual.should_not have_xxx(:arg) # passes if actual.has_xxx?(:arg)
+  # ```
+  #
+  # ### Ranges (Ruby >= 1.9 only)
+  #
+  # ```ruby
+  # (1..10).should cover(3)
+  # ```
+  #
+  # ### Collection membership
+  #
+  # ```ruby
+  # actual.should include(expected)
+  # actual.should start_with(expected)
+  # actual.should end_with(expected)
+  # ```
+  #
+  # #### Examples
+  #
+  # ```ruby
+  # [1,2,3].should       include(1)
+  # [1,2,3].should       include(1, 2)
+  # [1,2,3].should       start_with(1)
+  # [1,2,3].should       start_with(1,2)
+  # [1,2,3].should       end_with(3)
+  # [1,2,3].should       end_with(2,3)
+  # {:a => 'b'}.should   include(:a => 'b')
+  # "this string".should include("is str")
+  # "this string".should start_with("this")
+  # "this string".should end_with("ring")
+  # ```
+  module Should
+    module_function
+
+    # Enables the `should` syntax on the default host (Object's last ancestor).
+    def enable!
+      enable_should(default_should_host)
+    end
+
+    # @api private
+    # Determines where we add `should` and `should_not`.
+    def default_should_host
+      @default_should_host ||= ::Object.ancestors.last
+    end
+
+    # @api private
+    # Enables the `should` syntax.
+    def enable_should(syntax_host = default_should_host)
+      return if should_enabled?(syntax_host)
+
+      syntax_host.module_exec do
+        def should(matcher = nil, message = nil, &block)
+          ::RSpec::Expectations::PositiveExpectationHandler.handle_matcher(self, matcher, message, &block)
+        end
+
+        def should_not(matcher = nil, message = nil, &block)
+          ::RSpec::Expectations::NegativeExpectationHandler.handle_matcher(self, matcher, message, &block)
+        end
+      end
+    end
+
+    # @api private
+    # Indicates whether or not the `should` syntax is enabled.
+    def should_enabled?(syntax_host = default_should_host)
+      syntax_host.method_defined?(:should)
+    end
+  end
+end

data/script/bundle

@@ -0,0 +1,13 @@
+set -e
+
+SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
+source $SCRIPT_DIR/functions.sh
+
+echo "Set bundle path to .bundle/gems"
+bundle config set --local path '.bundle/gems'
+
+echo "bundle install --standalone"
+bundle install --standalone
+
+echo "bundle binstubs --all --standalone"
+bundle binstubs --all --standalone

data/script/check_documentation_coverage

@@ -0,0 +1,39 @@
+set -e
+
+ROOT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )/.." && pwd )"
+SCRIPT_DIR="${ROOT_DIR}/script"
+source $SCRIPT_DIR/functions.sh
+
+echo "bin/yard stats --list-undoc"
+
+$ROOT_DIR/bin/yard stats --list-undoc | ruby -e "
+  while line = gets
+    has_warnings ||= line.start_with?('[warn]:')
+    coverage ||= line[/([\d\.]+)% documented/, 1]
+    puts line
+  end
+
+  unless Float(coverage) == 100
+    puts \"\n\nMissing documentation coverage (currently at #{coverage}%)\"
+    exit(1)
+  end
+
+  if has_warnings
+    puts \"\n\nYARD emitted documentation warnings.\"
+    exit(1)
+  end
+"
+
+# Some warnings only show up when generating docs, so do that as well.
+$ROOT_DIR/bin/yard doc --no-cache | ruby -e "
+  while line = gets
+    has_warnings ||= line.start_with?('[warn]:')
+    has_errors   ||= line.start_with?('[error]:')
+    puts line
+  end
+
+  if has_warnings || has_errors
+    puts \"\n\nYARD emitted documentation warnings or errors.\"
+    exit(1)
+  end
+"

data/script/functions.sh

@@ -0,0 +1,10 @@
+ROOT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )/.." && pwd )"
+SCRIPT_DIR="${ROOT_DIR}/script"
+
+function is_ruby_31_plus {
+  if ruby -e "exit(RUBY_VERSION.to_f >= 3.1)"; then
+    return 0
+  else
+    return 1
+  fi
+}

data/script/update_rubygems_and_install_bundler

@@ -0,0 +1,14 @@
+set -e
+
+SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
+source $SCRIPT_DIR/functions.sh
+
+if is_ruby_31_plus; then
+  echo "Installing most recent rubygems / bundler"
+  yes | gem update --no-document --system
+  yes | gem install --no-document bundler
+else
+  echo "Installing rubygems 3.2.22 / bundler 2.2.22"
+  yes | gem update --system '3.2.22'
+  yes | gem install bundler -v '2.2.22'
+fi

metadata

@@ -0,0 +1,97 @@
+--- !ruby/object:Gem::Specification
+name: rspec-should
+version: !ruby/object:Gem::Version
+  version: 0.1.0.beta1
+platform: ruby
+authors:
+- Jon Rowe
+bindir: exe
+cert_chain:
+- |
+  -----BEGIN CERTIFICATE-----
+  MIIFvjCCA6agAwIBAgIJAPXjfUbCjdXWMA0GCSqGSIb3DQEBCwUAMIGAMQswCQYD
+  VQQGEwJVUzETMBEGA1UECAwKV2FzaGluZ3RvbjEQMA4GA1UEBwwHU2VhdHRsZTEO
+  MAwGA1UECgwFUlNwZWMxEzARBgNVBAMMCnJzcGVjLmluZm8xJTAjBgkqhkiG9w0B
+  CQEWFnJzcGVjQGdvb2dsZWdyb3Vwcy5jb20wHhcNMjYwMjE3MTE0ODM0WhcNMjcw
+  MjE3MTE0ODM0WjCBgDELMAkGA1UEBhMCVVMxEzARBgNVBAgMCldhc2hpbmd0b24x
+  EDAOBgNVBAcMB1NlYXR0bGUxDjAMBgNVBAoMBVJTcGVjMRMwEQYDVQQDDApyc3Bl
+  Yy5pbmZvMSUwIwYJKoZIhvcNAQkBFhZyc3BlY0Bnb29nbGVncm91cHMuY29tMIIC
+  IjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAsSmjgcHaKlD0jizRJowi2bGI
+  KMOHnJoExxRNHHxH+3w9kkl95YldvDRVX495b13ZCzwRe0AyqX24wq04tp0G5Z5C
+  e/w2pnNK4ol1eECPwQu+YGpepeODlZICL5gwQspe0cDifbBnHx5QySMiPpvx6bC0
+  tQTox0ppDIaMhch8IPCwyoE4DQK5bpsdwnLSHTsQjUIb7IM8tUMpd/iKrJgNffwc
+  6gC1TmhIlzQoB26nCNh9uK7xZjUM+sGECzvcYuImchUaIgJA/ybrlZS+m/hxzvBo
+  mLnn/xNEC6Vz5HG+3TR0Gb0cSUf6XUu2s51Jk/SJi3MhCZp2gs9OUg4EVZNzQVkZ
+  efLBjAZG2Mxk14JyB4/Omc+Jk0ajprINCBbUNnxzCJrYDM3J9TVWIwyUGNX/U3MO
+  s3tMAT+EVgx/mZMPnBO8EULlyF51MRUp3Wy9Mnw8AYLk30UnMG5AjqgO5JNyFlA7
+  Xeh3EVdWY3vMB1pkhPwlsenpcmj5gOzrd54lELOVbCGHCf48iSqeflY2Lhe0pvzK
+  blXCJBDmtrebvus291rM/dHcbEfK1SVd5Wut/n131iouf6dnNCFskFygDcgBbthC
+  gpEMqf80lEmhX59VUsm0Pv6OEo+ZPHBvXPiJA6DShQh9t3YtpwyA8uVDMbT/i32u
+  2FUsqZbbJcCmkBrGposCAwEAAaM5MDcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAw
+  HQYDVR0OBBYEFPPvQ5XT0Nvuhi6k+hrWVv35J+TeMA0GCSqGSIb3DQEBCwUAA4IC
+  AQBaeeGIZtBFDP33D1/4sXldSgwntVcL5qC5pcjamLWM4HK4/a6ePMy1uoX+dEnJ
+  J+BjZWURsUfFOob+xnUe8AMSbv9gupckfVehZoBzOvJDaWcALo8GKjJlmVtzEIqZ
+  TvBLO5zQwR4cWIrg0NWjkDOSQOrNNQ2Degv/aOFrR8dFPJSgxZG/IC0/t6s72cEt
+  V4SIe/NLIU4RyBzfgn/RBsalDEF1yIVlDWspMa78clS3bPmntkNyfLwIUwINDHhn
+  swFA8bEKMQWqRlupuRmEiy3nGe6az46YlPXzK5UWfXJ6Lb1wIE8W80TRx0HpSC7j
+  JfXPfQ0PLgiU4nnQqain2bIn96Ooco8kspeqp8rSJ8sbaMPTNmcFuwD3gzWsRnJ3
+  rIaJbmrUcq6DlJ7jfv3u5TPt4JWzDP7oDPf3nXNiF2Cn48Ne598G5lHH6Heyxe39
+  pYZdhEptKJWPHxbJWHXD02omKprkNuQKHpnXrW+mmbiO4IcqAMggiud+DaEQg20x
+  Dae4cNbvK5p3D+5xqvcEO2G4uCMDmJjrSd61kvTLBnm1qroHqrpi9GauEVWZZmD0
+  n0ph8oFAXOsKQWxZ+4uh6yGISk+WhngCZEVPZUjq7SIGAuVhQy2ZgwdjnLEz//lD
+  x0Qexp5yGeoxAL9qKM/RXYKtuRZBJV1z+L9A1YOtwaXXNg==
+  -----END CERTIFICATE-----
+date: 1980-01-02 00:00:00.000000000 Z
+dependencies: []
+description: "`should` syntax for RSpec 4.0.x"
+email: rspec@googlegroups.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".github/workflows/ci.yml"
+- ".github/workflows/documentation_coverage.yml"
+- ".github/workflows/rspec.yml"
+- ".github/workflows/rubocop.yml"
+- ".yardopts"
+- CODE_OF_CONDUCT.md
+- Changelog.md
+- LICENSE.md
+- README.md
+- Rakefile
+- lib/rspec/should.rb
+- lib/rspec/should/enable.rb
+- lib/rspec/should/version.rb
+- script/bundle
+- script/check_documentation_coverage
+- script/functions.sh
+- script/update_rubygems_and_install_bundler
+homepage: https://rspec.info
+licenses:
+- MIT
+metadata:
+  bug_tracker_uri: https://github.com/rspec/rspec-should/issues
+  changelog_uri: https://github.com/rspec/rspec-should/tree/v0.1.0.beta1/Changelog.md
+  documentation_uri: https://rspec.info/documentation/
+  homepage_uri: https://rspec.info
+  mailing_list_uri: https://groups.google.com/forum/#!forum/rspec
+  rubygems_mfa_required: 'true'
+  source_code_uri: https://github.com/rspec/rspec-should
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 3.0.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 4.0.6
+specification_version: 4
+summary: rspec-should-0.1.0.beta1
+test_files: []

metadata.gz.sig

@@ -0,0 +1,3 @@
+Z�mK �)NɀQP���
0�
+8�pY�h�Ҧ�{�F}�0k�������K�:f���M��<�&o0J���H�xK�T�`�M��I�I��%\>�7	�#�K?�S��RY*_�b)��LlH���ZL���m���
+�bD�Id6����3D[�%oǖ&$:~,ʺ6���M�:3���>���f[��-No��{U�X�BF��-E�!s�fO���[��Z�<��@�'w�Ę�SR�OA紜
?{���m)�M��