timecop-rspec 1.0.2 → 1.0.3

data/.junie/guidelines.md

@@ -1,139 +0,0 @@
-Project: timecop-rspec — Development Guidelines (for advanced contributors)
-
-This document captures project-specific knowledge to streamline setup, testing, and ongoing development.
-
-1. Build and configuration
-- ENV is controlled by `direnv`.
-  - Two files are loaded:
-    - .envrc — environment variables for local development, committed to source control
-    - .env.local — environment variables that are not committed to source control. These setting override .envrc.
-  - Run `direnv allow` after making changes to .envrc or .env.local.
-    - See .envrc for details.
-    - See .env.local.example for an example of what to put in .env.local.
-    - See CONTRIBUTING.md for details on how to set up your local environment.
-- Ruby and Bundler
-  - Runtime supports very old Rubies (>= 1.9.2) but development tooling targets >= 2.3 because of CI/setup-ruby and dev dependencies.
-  - Use a recent Ruby (>= 3.1 recommended) for fastest setup and to exercise modern coverage behavior.
-  - Install dependencies via Bundler in project root:
-    - bundle install
-- Rake tasks (preferred entry points)
-  - The Rakefile wires common workflows. Useful targets:
-    - rake spec — run RSpec suite (also aliased via rake test)
-    - rake coverage — run specs with coverage locally and open a report (requires kettle-soup-cover)
-    - rake rubocop_gradual:autocorrect — RuboCop-LTS Gradual, with autocorrect as default task
-    - rake reek and rake reek:update — code smell checks and persisted snapshots in REEK
-    - rake yard — generate YARD docs for lib and selected extra files
-    - rake bundle:audit and rake bundle:audit:update — dependency vulnerability checks
-    - rake build / rake release — gem build/release helper tasks (Bundler + stone_checksums)
-  - The default rake target runs a curated set of tasks; this varies for CI vs local (see CI env var logic in Rakefile).
-    - Always run the default rake task prior commits, and after making changes to lib/ code, or *.md files, to allow the linter to autocorrect, and to generate updated documentation..
-- Coverage orchestration
-  - Coverage is controlled by kettle-soup-cover and .simplecov. Thresholds (line and branch) are enforced and can fail the process.
-  - Thresholds are primarily controlled by environment variables (see .simplecov and comments therein) typically loaded via direnv (.envrc) and CI workflow (.github/workflows/coverage.yml). When running only a test subset, thresholds may fail; see Testing below.
-- Gem signing (for releases)
-  - Signing is enabled unless SKIP_GEM_SIGNING is set. If enabled and certificates are present (certs/<USER>.pem), gem build will attempt to sign using ~/.ssh/gem-private_key.pem.
-  - See CONTRIBUTING.md for releasing details; use SKIP_GEM_SIGNING when building in environments without the private key.
-
-2. Testing
-- Framework and helpers
-  - RSpec 3.13 with custom spec/spec_helper.rb configuration:
-    - silent_stream: STDOUT is silenced by default for examples to keep logs clean.
-      - To explicitly test console output, tag the example or group with :check_output.
-    - Global state hygiene: Around each example, FlossFunding.namespaces and FlossFunding.silenced are snapshotted and restored to prevent cross-test pollution.
-    - DEBUG toggle: Set DEBUG=true to require 'debug' and avoid silencing output during your run.
-    - ENV seeding: The suite sets ENV["FLOSS_FUNDING_FLOSS_FUNDING"] = "Free-as-in-beer" so that the library’s own namespace is considered activated (avoids noisy warnings).
-    - Coverage: kettle-soup-cover integrates SimpleCov; .simplecov is invoked from spec_helper when enabled by Kettle::Soup::Cover::DO_COV, which is controlled by K_SOUP_COV_DO being set to true / false.
-    - RSpec.describe usage:
-      - Use `describe "#<method_name>"` to contain a block of specs that test instance method behavior.
-      - Use `describe "::<method_name>"` to contain a block of specs that test class method behavior.
-      - Do not use `describe ".<method_name>"` because the dot is ambiguous w.r.t instance vs. class methods. 
-    - When adding new code or modifying existing code always add tests to cover the updated behavior, including branches, and different types of expected and unexpected inputs.
-  - Additional test utilities:
-    - rspec-stubbed_env: Use stub_env to control ENV safely within examples.
-    - timecop: Time manipulation available via spec/config/timecop.
-    - support/bench_gems_generator: Utilities for benchmarking fixtures.
-- Running tests (verified)
-  - Full suite (recommended to satisfy coverage thresholds):
-    - bin/rspec
-    - or: bundle exec rspec
-    - or: bundle exec rake spec
-  - Progress format (less verbose):
-    - bundle exec rspec --format progress
-  - Focused runs
-    - You can run a single file or example, but note: coverage thresholds need to be disabled with K_SOUP_COV_MIN_HARD=false
-    - Example: K_SOUP_COV_MIN_HARD=false bin/rspec spec/timecop-rspec/class_spec.rb:42
-  - Output visibility
-    - To see STDOUT from the code under test, use the :check_output tag on the example or group.
-      Example:
-      RSpec.describe "output", :check_output do
-        it "prints" do
-          puts "This output should be visible"
-          expect(true).to be true
-        end
-      end
-    - Alternatively, run with DEBUG=true to disable silencing for the entire run.
-  - During a spec run, the presence of output about missing activation keys is often expected, since it is literally what this library is for. It only indicates a failure if the spec expected all activation keys to be present, and not all specs do.
-- Adding new tests (guidelines)
-  - Organize specs by class/module. Do not create per-task umbrella spec files; add examples to the existing spec for the class/module under test, or create a new spec file for that class/module if one does not exist. Only create a standalone scenario spec when it intentionally spans multiple classes for an integration/benchmark scenario (e.g., bench_integration_spec), and name it accordingly.
-  - Add tests for all public methods and add contexts for variations of their arguments, and arity.
-  - Place new specs under spec/ mirroring lib/ structure where possible. Do not require "spec_helper" at the top of spec files, as it is automatically loaded by .rspec.
-  - If your code relies on environment variables that drive activation (see "Activation env vars" below), prefer using rspec-stubbed_env:
-    - it does not support stubbing with blocks, but it does automatically clean up after itself.
-    - outside the example:
-      include_context 'with stubbed env'
-    - in a before hook, or in an example:
-      stub_env("FLOSS_FUNDING_MY_NS" => "Free-as-in-beer")
-      # example code continues
-  - If your spec needs to assert on console output, tag it with :check_output. By default, STDOUT is silenced.
-  - Use Timecop for deterministic time-sensitive behavior as needed (require config/timecop is already done by spec_helper).
-- Demonstrated example (executed and verified during this session)
-  - Example spec content used:
-    - File: spec/timecop-rspec/demo_spec.rb
-      RSpec.describe "Demo test for guidelines" do
-        it "has a non-empty version string" do
-          expect(FlossFunding::Version::VERSION).to be_a(String)
-          expect(FlossFunding::Version::VERSION).not_to be_empty
-        end
-      end
-  - Commands run:
-    - bundle exec rspec spec/timecop-rspec/demo_spec.rb — this ran but failed coverage thresholds (expected when running subsets with coverage on).
-    - bundle exec rspec — running the full suite including the demo spec passed; overall coverage: ~93.67% lines, ~74.07% branches.
-  - Cleanup: The demo spec file was removed after verification per instructions.
-
-3. Additional development information
-- Activation env vars and namespacing (important for tests and local runs)
-  - The library behavior is driven by namespace-based activation keys: ENV["FLOSS_FUNDING_<NAMESPACE>"].
-  - The FlossFunding::Namespace class derives env var names via FlossFunding::UnderBar.env_variable_name(name). Recognized activation forms include:
-    - Free-as-in-beer, Business-is-not-good-yet, or NOT-FINANCIALLY-SUPPORTING-<namespace> — treated as unpaid/opted-out and considered "activated" for silent success (no console warnings).
-    - A paid activation key is a 64-char hex string; it is decrypted with AES-256-CBC using a key derived from Digest::MD5.hexdigest(namespace).
-  - In tests, avoid noisy output and unrelated failures by either using the provided default (ENV seeded for this gem) or stubbing the relevant ENV vars for the namespaces you trigger.
-- Code style and static analysis
-  - RuboCop-LTS (Gradual) is integrated. Use:
-    - bundle exec rake rubocop_gradual:autocorrect
-    - bundle exec rake rubocop_gradual:force_update # only run if there are still linting violations the default rake task, which includes autocorrect locally, or a standalone autocorrect task, has run, and failed, and the violations won't be fixed
-  - Reek is configured to scan {lib,spec,tests}/**/*.rb. Use:
-    - bundle exec rake reek
-    - bundle exec rake reek:update              # writes current output to REEK, fails on smells
-    - Keep REEK file updated with intentional smells snapshot when appropriate (e.g., after refactors).
-    - Locally, the default rake task includes reek:update.
-- Documentation
-  - Generate YARD docs with: bundle exec rake yard. It includes lib/**/*.rb and extra docs like README.md, CHANGELOG.md, RUBOCOP.md, REEK, etc.
-- Appraisal and multi-gemfile testing
-  - appraisal2 is present to manage multiple dependency sets; see Appraisals and gemfiles/modular/*.gemfile. If you need to verify against alternate dependency versions, use Appraisal to install and run rspec under those Gemfiles.
-  - You can run a single github workflow by running `act -W /github/workflows/<workflow name>.yml`
-- CI/local differences and defaults
-  - The Rakefile adjusts default tasks based on CI env var. Locally, rake default may include coverage, reek:update, yard, etc. On CI, it tends to just run spec.
-
-Quick start
-1) bundle install
-2) K_SOUP_COV_FORMATTERS="xml,rcov,lcov,json" bin/rspec (generates coverage reports in coverage/ in the specified formats, only choose the formats you need)
-3) Optional local HTML coverage report: K_SOUP_COV_FORMATTERS="html" bin/rspec (generates HTML coverage report in coverage/ - but this is too verbose for AI, so Junie should use one of the more terse formats, like rcov, lcov, or json)
-4) Static analysis: bundle exec rake rubocop_gradual:check && bundle exec rake reek
-
-Notes
-- ALWAYS Run bundle exec rake rubocop_gradual:autocorrect as the final step before completing a task, to lint and autocorrect any remaining issues. Then if there are new lint failures, attempt to correct them manually.
-- NEVER run vanilla rubocop, as it won't handle the linting config properly. Always run rubocop_gradual:autocorrect or rubocop_gradual.
-- NEVER consider backwards compatibility when adding new features or refactoring existing code, as this library is in the design phase, and is still an alpha release.
-- Running only a subset of specs is supported but in order to bypass the hard failure due to coverage thresholds, you need to run with K_SOUP_COV_MIN_HARD=false.
-- When adding code that writes to STDOUT, remember most specs silence output unless tagged with :check_output or DEBUG=true.
-- For all the kettle-soup-cover options, see .envrc and find the K_SOUP_COV_* env vars.

data/.qlty/qlty.toml

@@ -1,79 +0,0 @@
-# For a guide to configuration, visit https://qlty.sh/d/config
-# Or for a full reference, visit https://qlty.sh/d/qlty-toml
-config_version = "0"
-
-exclude_patterns = [
-  "*_min.*",
-  "*-min.*",
-  "*.min.*",
-  "**/.yarn/**",
-  "**/*.d.ts",
-  "**/assets/**",
-  "**/bin/**",
-  "**/bower_components/**",
-  "**/build/**",
-  "**/cache/**",
-  "**/config/**",
-  "**/.devcontainer",
-  "**/db/**",
-  "**/deps/**",
-  "**/dist/**",
-  "**/doc/**",
-  "**/docs/**",
-  "**/extern/**",
-  "**/external/**",
-  "**/generated/**",
-  "**/Godeps/**",
-  "**/gradlew/**",
-  "**/mvnw/**",
-  "**/node_modules/**",
-  "**/protos/**",
-  "**/seed/**",
-  "**/target/**",
-  "**/templates/**",
-  "**/testdata/**",
-  "**/vendor/**",
-  ".github/workflows/codeql-analysis.yml"
-]
-
-test_patterns = [
-  "**/test/**",
-  "**/spec/**",
-  "**/*.test.*",
-  "**/*.spec.*",
-  "**/*_test.*",
-  "**/*_spec.*",
-  "**/test_*.*",
-  "**/spec_*.*",
-]
-
-[smells]
-mode = "comment"
-
-[smells.boolean_logic]
-threshold = 4
-enabled = true
-
-[smells.file_complexity]
-threshold = 55
-enabled = false
-
-[smells.return_statements]
-threshold = 4
-enabled = true
-
-[smells.nested_control_flow]
-threshold = 4
-enabled = true
-
-[smells.function_parameters]
-threshold = 4
-enabled = true
-
-[smells.function_complexity]
-threshold = 5
-enabled = true
-
-[smells.duplication]
-enabled = true
-threshold = 20

data/.rspec

@@ -1,8 +0,0 @@
---format progress
---color
---require spec_helper
---warnings
---format html
---out results/test_results.html
---format RspecJunitFormatter
---out results/test_results.xml

data/.rubocop.yml

@@ -1,15 +0,0 @@
-inherit_gem:
-  rubocop-lts: config/rubygem_rspec.yml
-
-AllCops:
-  Exclude:
-    - 'spec/fixtures/gem_mine/**/*'
-    - 'spec/fixtures/gemspecs/**/*'
-    - 'spec/fixtures/non_gems/**/*'
-    - 'spec/fixtures/scenario_gems/**/*'
-
-RSpec/ExampleLength:
-  Enabled: false
-
-Layout/IndentationConsistency:
-  Exclude: ['*.md']

data/.rubocop_gradual.lock

@@ -1,76 +0,0 @@
-{
-  "Rakefile:2312831157": [
-    [70, 5, 15, "Rake/Desc: Describe the task with `desc` method.", 842824456]
-  ],
-  "lib/timecop/rspec.rb:1066485176": [
-    [42, 9, 12, "ThreadSafety/ClassInstanceVariable: Avoid class instance variables.", 990613604]
-  ],
-  "lib/timecop/rspec/sequential_time_machine.rb:3576394007": [
-    [15, 7, 53, "Style/ClassMethodsDefinitions: Use `class << self` to define a class method.", 496991953],
-    [16, 9, 9, "ThreadSafety/ClassInstanceVariable: Avoid class instance variables.", 356709996]
-  ],
-  "lib/timecop/rspec/time_machine.rb:1233248191": [
-    [11, 7, 53, "Style/ClassMethodsDefinitions: Use `class << self` to define a class method.", 496991953],
-    [12, 9, 9, "ThreadSafety/ClassInstanceVariable: Avoid class instance variables.", 356709996]
-  ],
-  "spec/timecop/rspec/a_time_machine.rb:3434657420": [
-    [25, 13, 29, "RSpec/ContextWording: Context description should match /^when\\b/, /^with\\b/, or /^without\\b/.", 2090924979],
-    [28, 7, 64, "RSpec/MultipleExpectations: Example has too many expectations [2/1].", 1461883873],
-    [31, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [38, 7, 56, "RSpec/MultipleExpectations: Example has too many expectations [2/1].", 643029529],
-    [42, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [49, 7, 53, "RSpec/MultipleExpectations: Example has too many expectations [2/1].", 3086872678],
-    [53, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [60, 7, 124, "RSpec/MultipleExpectations: Example has too many expectations [6/1].", 676965629],
-    [64, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [69, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [74, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [80, 7, 36, "RSpec/MultipleExpectations: Example has too many expectations [2/1].", 1669892008],
-    [84, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [90, 7, 42, "RSpec/MultipleExpectations: Example has too many expectations [2/1].", 2672670916],
-    [91, 23, 33, "Style/DateTime: Prefer `Time` over `DateTime`.", 2306291980],
-    [94, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [103, 7, 62, "RSpec/MultipleExpectations: Example has too many expectations [5/1].", 1809499334],
-    [104, 23, 25, "Style/DateTime: Prefer `Time` over `DateTime`.", 2011980225],
-    [111, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [120, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [126, 7, 131, "RSpec/MultipleExpectations: Example has too many expectations [6/1].", 2099780707],
-    [130, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [135, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [140, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [146, 15, 35, "RSpec/ContextWording: Context description should match /^when\\b/, /^with\\b/, or /^without\\b/.", 710711823],
-    [147, 9, 81, "RSpec/MultipleExpectations: Example has too many expectations [2/1].", 262796784],
-    [149, 30, 8, "RSpec/InstanceVariable: Avoid instance variables - use let, a method call, or a local variable (if possible).", 2321415930],
-    [152, 37, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [159, 9, 78, "RSpec/MultipleExpectations: Example has too many expectations [2/1].", 2987422127],
-    [161, 30, 8, "RSpec/InstanceVariable: Avoid instance variables - use let, a method call, or a local variable (if possible).", 2321981723],
-    [164, 37, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [173, 13, 28, "RSpec/ContextWording: Context description should match /^when\\b/, /^with\\b/, or /^without\\b/.", 830037094],
-    [176, 7, 48, "RSpec/MultipleExpectations: Example has too many expectations [2/1].", 1915717479],
-    [177, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [187, 7, 70, "RSpec/MultipleExpectations: Example has too many expectations [2/1].", 3183424212],
-    [191, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [198, 7, 70, "RSpec/MultipleExpectations: Example has too many expectations [2/1].", 1685240264],
-    [202, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [209, 7, 67, "RSpec/MultipleExpectations: Example has too many expectations [2/1].", 4130782052],
-    [213, 35, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950]
-  ],
-  "spec/timecop/rspec/sequential_time_machine_spec.rb:2709164453": [
-    [19, 3, 124, "RSpec/MultipleExpectations: Example has too many expectations [6/1].", 676965629],
-    [24, 31, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [29, 31, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [34, 31, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [44, 11, 28, "RSpec/ContextWording: Context description should match /^when\\b/, /^with\\b/, or /^without\\b/.", 830037094],
-    [52, 5, 72, "RSpec/MultipleExpectations: Example has too many expectations [6/1].", 2221852238],
-    [54, 33, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [59, 33, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950],
-    [64, 33, 7, "RSpec/MessageSpies: Prefer `have_received` for setting message expectations. Setup `example_procsy` as a spy using `allow` or `instance_spy`.", 1384559950]
-  ],
-  "timecop-rspec.gemspec:2892863758": [
-    [111, 3, 3, "Gemspec/DuplicatedAssignment: `files=` method calls already given on line 65 of the gemspec.", 193433027],
-    [111, 16, 19, "Packaging/GemspecGit: Avoid using git to produce lists of files. Downstreams often need to build your package in an environment that does not have git (on purpose). Use some pure Ruby alternative, like `Dir` or `Dir.glob`.", 3879951891],
-    [114, 3, 19, "Gemspec/DuplicatedAssignment: `bindir=` method calls already given on line 107 of the gemspec.", 554494033],
-    [115, 3, 70, "Gemspec/DuplicatedAssignment: `executables=` method calls already given on line 109 of the gemspec.", 18210340],
-    [116, 3, 28, "Gemspec/DuplicatedAssignment: `require_paths=` method calls already given on line 106 of the gemspec.", 1947597918]
-  ]
-}

data/.simplecov

@@ -1,11 +0,0 @@
-require "kettle/soup/cover/config"
-
-# Minimum coverage thresholds are set by kettle-soup-cover.
-# It is controlled by ENV variables, which are set in .envrc and loaded via `direnv allow`
-# If the values for minimum coverage need to change, they should be changed both there,
-#   and in 2 places in .github/workflows/coverage.yml.
-SimpleCov.start do
-  # GemMine is only used in the test framework.
-  # It isn't the focus of this library anyway.
-  add_filter "lib/gem_mine"
-end

data/.tool-versions

@@ -1 +0,0 @@
-ruby 3.4.5

data/.yard_gfm_support.rb

@@ -1,22 +0,0 @@
-# Gratefully and liberally taken from the MIT-licensed https://github.com/bensheldon/good_job/pull/113/files
-require "kramdown"
-require "kramdown-parser-gfm"
-
-# Custom markup provider class that always renders Kramdown using GFM (Github Flavored Markdown).
-# GFM is needed to render markdown tables and fenced code blocks in the README.
-class KramdownGfmDocument < Kramdown::Document
-  def initialize(source, options = {})
-    options[:input] = "GFM" unless options.key?(:input)
-    super(source, options)
-  end
-end
-
-# Insert the new provider as the highest priority option for Markdown.
-# See:
-# - https://github.com/lsegal/yard/issues/1157
-# - https://github.com/lsegal/yard/issues/1017
-# - https://github.com/lsegal/yard/blob/main/lib/yard/templates/helpers/markup_helper.rb
-YARD::Templates::Helpers::MarkupHelper::MARKUP_PROVIDERS[:markdown].insert(
-  0,
-  {:const => "KramdownGfmDocument"},
-)

data/.yardopts

@@ -1,11 +0,0 @@
---plugin junk
---plugin relative_markdown_links
---readme README.md
---charset utf-8
---markup markdown
---output docs
---load .yard_gfm_support.rb
-'lib/**/*.rb'
--
-'*.md'
-'*.txt'

data/Appraisal.root.gemfile

@@ -1,12 +0,0 @@
-# frozen_string_literal: true
-
-git_source(:github) { |repo_name| "https://github.com/#{repo_name}" }
-
-source "https://rubygems.org"
-
-# Appraisal Root Gemfile is for running appraisal to generate the Appraisal Gemfiles
-#   in gemfiles/*gemfile.
-# On CI, we use it for the Appraisal-based builds.
-# We do not load the standard Gemfile, as it is tailored for local development.
-
-gemspec

data/Appraisals

@@ -1,104 +0,0 @@
-# frozen_string_literal: true
-
-# HOW TO UPDATE APPRAISALS:
-#   BUNDLE_GEMFILE=Appraisal.root.gemfile bundle
-#   BUNDLE_GEMFILE=Appraisal.root.gemfile bundle exec appraisal update
-#   bundle exec rake rubocop_gradual:autocorrect
-
-# Lock/Unlock Deps Pattern
-#
-# Two often conflicting goals resolved!
-#
-#  - deps_unlocked.yml
-#    - All runtime & dev dependencies, but does not have a `gemfiles/*.gemfile.lock` committed
-#    - Uses an Appraisal2 "deps_unlocked" gemfile, and the current MRI Ruby release
-#    - Know when new dependency releases will break local dev with unlocked dependencies
-#    - Broken workflow indicates that new releases of dependencies may not work
-#
-#  - deps_locked.yml
-#    - All runtime & dev dependencies, and has a `Gemfile.lock` committed
-#    - Uses the project's main Gemfile, and the current MRI Ruby release
-#    - Matches what contributors and maintainers use locally for development
-#    - Broken workflow indicates that a new contributor will have a bad time
-#
-appraise "deps_unlocked" do
-  eval_gemfile "modular/audit.gemfile"
-  eval_gemfile "modular/coverage.gemfile"
-  eval_gemfile "modular/documentation.gemfile"
-  eval_gemfile "modular/style.gemfile"
-end
-
-# Used for head (nightly) releases of ruby, truffleruby, and jruby.
-# Split into discrete appraisals if one of them needs a dependency locked discretely.
-appraise "head" do
-  gem "mutex_m", ">= 0.2"
-  gem "stringio", ">= 3.0"
-  gem "benchmark", "~> 0.4", ">= 0.4.1"
-end
-
-# Used for current releases of ruby, truffleruby, and jruby.
-# Split into discrete appraisals if one of them needs a dependency locked discretely.
-appraise "current" do
-  gem "mutex_m", ">= 0.2"
-  gem "stringio", ">= 3.0"
-end
-
-appraise "ruby-2-3" do
-end
-
-appraise "ruby-2-4" do
-end
-
-appraise "ruby-2-5" do
-end
-
-appraise "ruby-2-6" do
-  gem "mutex_m", "~> 0.2"
-  gem "stringio", "~> 3.0"
-end
-
-appraise "ruby-2-7" do
-  gem "mutex_m", "~> 0.2"
-  gem "stringio", "~> 3.0"
-end
-
-appraise "ruby-3-0" do
-  gem "mutex_m", "~> 0.2"
-  gem "stringio", "~> 3.0"
-end
-
-appraise "ruby-3-1" do
-  gem "mutex_m", "~> 0.2"
-  gem "stringio", "~> 3.0"
-end
-
-appraise "ruby-3-2" do
-  gem "mutex_m", "~> 0.2"
-  gem "stringio", "~> 3.0"
-end
-
-appraise "ruby-3-3" do
-  gem "mutex_m", "~> 0.2"
-  gem "stringio", "~> 3.0"
-end
-
-# Only run security audit on latest Ruby version
-appraise "audit" do
-  gem "mutex_m", "~> 0.2"
-  gem "stringio", "~> 3.0"
-  eval_gemfile "modular/audit.gemfile"
-end
-
-# Only run coverage on latest Ruby version
-appraise "coverage" do
-  gem "mutex_m", "~> 0.2"
-  gem "stringio", "~> 3.0"
-  eval_gemfile "modular/coverage.gemfile"
-end
-
-# Only run linter on latest Ruby version (but, in support of oldest supported Ruby version)
-appraise "style" do
-  gem "mutex_m", "~> 0.2"
-  gem "stringio", "~> 3.0"
-  eval_gemfile "modular/style.gemfile"
-end

data/CNAME

@@ -1 +0,0 @@
-timecop-rspec.galtzo.com

data/Gemfile

@@ -1,38 +0,0 @@
-# frozen_string_literal: true
-
-source "https://rubygems.org"
-
-git_source(:github) { |repo_name| "https://github.com/#{repo_name}" }
-git_source(:gitlab) { |repo_name| "https://gitlab.com/#{repo_name}" }
-
-#### IMPORTANT #######################################################
-# Gemfile is for local development ONLY; Gemfile is NOT loaded in CI #
-####################################################### IMPORTANT ####
-
-# Include dependencies from <gem name>.gemspec
-gemspec
-
-platform :mri do
-  # Debugging - Ensure ENV["DEBUG"] == "true" to use debuggers within spec suite
-  # Use binding.break, binding.b, or debugger in code
-  gem "debug", ">= 1.0.0"                  # ruby >= 2.7
-  gem "gem_bench", "~> 2.0", ">= 2.0.5"
-
-  # Dev Console - Binding.pry - Irb replacement
-  gem "pry", "~> 0.14"                     # ruby >= 2.0
-end
-
-# optional dependency for debug logging
-gem "logger"
-
-# Security Audit
-eval_gemfile "gemfiles/modular/audit.gemfile"
-
-# Code Coverage
-eval_gemfile "gemfiles/modular/coverage.gemfile"
-
-# Linting
-eval_gemfile "gemfiles/modular/style.gemfile"
-
-# Documentation
-eval_gemfile "gemfiles/modular/documentation.gemfile"