diff-lcs 1.5.0 → 1.6.0

data/spec/traverse_sequences_spec.rb

@@ -1,10 +1,10 @@
 # frozen_string_literal: true
 
-require 'spec_helper'
+require "spec_helper"
 
-describe 'Diff::LCS.traverse_sequences' do
-  describe 'callback with no finishers' do
-    describe 'over (seq1, seq2)' do
+describe "Diff::LCS.traverse_sequences" do
+  describe "callback with no finishers" do
+    describe "over (seq1, seq2)" do
       before(:each) do
         @callback_s1_s2 = simple_callback_no_finishers
         Diff::LCS.traverse_sequences(seq1, seq2, @callback_s1_s2)
@@ -13,27 +13,27 @@ describe 'Diff::LCS.traverse_sequences' do
         Diff::LCS.traverse_sequences(seq2, seq1, @callback_s2_s1)
       end
 
-      it 'has the correct LCS result on left-matches' do
+      it "has the correct LCS result on left-matches" do
         expect(@callback_s1_s2.matched_a).to eq(correct_lcs)
         expect(@callback_s2_s1.matched_a).to eq(correct_lcs)
       end
 
-      it 'has the correct LCS result on right-matches' do
+      it "has the correct LCS result on right-matches" do
         expect(@callback_s1_s2.matched_b).to eq(correct_lcs)
         expect(@callback_s2_s1.matched_b).to eq(correct_lcs)
       end
 
-      it 'has the correct skipped sequences with the left sequence' do
+      it "has the correct skipped sequences with the left sequence" do
         expect(@callback_s1_s2.discards_a).to eq(skipped_seq1)
         expect(@callback_s2_s1.discards_a).to eq(skipped_seq2)
       end
 
-      it 'has the correct skipped sequences with the right sequence' do
+      it "has the correct skipped sequences with the right sequence" do
         expect(@callback_s1_s2.discards_b).to eq(skipped_seq2)
         expect(@callback_s2_s1.discards_b).to eq(skipped_seq1)
       end
 
-      it 'does not have anything done markers from the left or right sequences' do
+      it "does not have anything done markers from the left or right sequences" do
         expect(@callback_s1_s2.done_a).to be_empty
         expect(@callback_s1_s2.done_b).to be_empty
         expect(@callback_s2_s1.done_a).to be_empty
@@ -41,64 +41,64 @@ describe 'Diff::LCS.traverse_sequences' do
       end
     end
 
-    describe 'over (hello, hello)' do
+    describe "over (hello, hello)" do
       before(:each) do
         @callback = simple_callback_no_finishers
         Diff::LCS.traverse_sequences(hello, hello, @callback)
       end
 
-      it 'has the correct LCS result on left-matches' do
-        expect(@callback.matched_a).to eq(hello.split(//))
+      it "has the correct LCS result on left-matches" do
+        expect(@callback.matched_a).to eq(hello.chars)
       end
 
-      it 'has the correct LCS result on right-matches' do
-        expect(@callback.matched_b).to eq(hello.split(//))
+      it "has the correct LCS result on right-matches" do
+        expect(@callback.matched_b).to eq(hello.chars)
       end
 
-      it 'has the correct skipped sequences with the left sequence', :only => true do
+      it "has the correct skipped sequences with the left sequence" do
         expect(@callback.discards_a).to be_empty
       end
 
-      it 'has the correct skipped sequences with the right sequence' do
+      it "has the correct skipped sequences with the right sequence" do
         expect(@callback.discards_b).to be_empty
       end
 
-      it 'does not have anything done markers from the left or right sequences' do
+      it "does not have anything done markers from the left or right sequences" do
         expect(@callback.done_a).to be_empty
         expect(@callback.done_b).to be_empty
       end
     end
 
-    describe 'over (hello_ary, hello_ary)' do
+    describe "over (hello_ary, hello_ary)" do
       before(:each) do
         @callback = simple_callback_no_finishers
         Diff::LCS.traverse_sequences(hello_ary, hello_ary, @callback)
       end
 
-      it 'has the correct LCS result on left-matches' do
+      it "has the correct LCS result on left-matches" do
         expect(@callback.matched_a).to eq(hello_ary)
       end
 
-      it 'has the correct LCS result on right-matches' do
+      it "has the correct LCS result on right-matches" do
         expect(@callback.matched_b).to eq(hello_ary)
       end
 
-      it 'has the correct skipped sequences with the left sequence' do
+      it "has the correct skipped sequences with the left sequence" do
         expect(@callback.discards_a).to be_empty
       end
 
-      it 'has the correct skipped sequences with the right sequence' do
+      it "has the correct skipped sequences with the right sequence" do
         expect(@callback.discards_b).to be_empty
       end
 
-      it 'does not have anything done markers from the left or right sequences' do
+      it "does not have anything done markers from the left or right sequences" do
         expect(@callback.done_a).to be_empty
         expect(@callback.done_b).to be_empty
       end
     end
   end
 
-  describe 'callback with finisher' do
+  describe "callback with finisher" do
     before(:each) do
       @callback_s1_s2 = simple_callback
       Diff::LCS.traverse_sequences(seq1, seq2, @callback_s1_s2)
@@ -106,32 +106,32 @@ describe 'Diff::LCS.traverse_sequences' do
       Diff::LCS.traverse_sequences(seq2, seq1, @callback_s2_s1)
     end
 
-    it 'has the correct LCS result on left-matches' do
+    it "has the correct LCS result on left-matches" do
       expect(@callback_s1_s2.matched_a).to eq(correct_lcs)
       expect(@callback_s2_s1.matched_a).to eq(correct_lcs)
     end
 
-    it 'has the correct LCS result on right-matches' do
+    it "has the correct LCS result on right-matches" do
       expect(@callback_s1_s2.matched_b).to eq(correct_lcs)
       expect(@callback_s2_s1.matched_b).to eq(correct_lcs)
     end
 
-    it 'has the correct skipped sequences for the left sequence' do
+    it "has the correct skipped sequences for the left sequence" do
       expect(@callback_s1_s2.discards_a).to eq(skipped_seq1)
       expect(@callback_s2_s1.discards_a).to eq(skipped_seq2)
     end
 
-    it 'has the correct skipped sequences for the right sequence' do
+    it "has the correct skipped sequences for the right sequence" do
       expect(@callback_s1_s2.discards_b).to eq(skipped_seq2)
       expect(@callback_s2_s1.discards_b).to eq(skipped_seq1)
     end
 
-    it 'has done markers differently-sized sequences' do
-      expect(@callback_s1_s2.done_a).to eq([['p', 9, 't', 11]])
+    it "has done markers differently-sized sequences" do
+      expect(@callback_s1_s2.done_a).to eq([["p", 9, "t", 11]])
       expect(@callback_s1_s2.done_b).to be_empty
 
       expect(@callback_s2_s1.done_a).to be_empty
-      expect(@callback_s2_s1.done_b).to eq([['t', 11, 'p', 9]])
+      expect(@callback_s2_s1.done_b).to eq([["t", 11, "p", 9]])
     end
   end
 end

metadata

@@ -1,15 +1,35 @@
 --- !ruby/object:Gem::Specification
 name: diff-lcs
 version: !ruby/object:Gem::Version
-  version: 1.5.0
+  version: 1.6.0
 platform: ruby
 authors:
 - Austin Ziegler
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-12-23 00:00:00.000000000 Z
+date: 2025-02-13 00:00:00.000000000 Z
 dependencies:
+- !ruby/object:Gem::Dependency
+  name: hoe
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '3.0'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '5'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '3.0'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '5'
 - !ruby/object:Gem::Dependency
   name: hoe-doofus
   requirement: !ruby/object:Gem::Requirement
@@ -39,19 +59,19 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '1.1'
 - !ruby/object:Gem::Dependency
-  name: hoe-git
+  name: hoe-git2
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.6'
+        version: '1.7'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.6'
+        version: '1.7'
 - !ruby/object:Gem::Dependency
   name: hoe-rubygems
   requirement: !ruby/object:Gem::Requirement
@@ -127,33 +147,33 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '7'
 - !ruby/object:Gem::Dependency
-  name: hoe
+  name: simplecov
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.23'
+        version: '0.21'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.23'
+        version: '0.21'
 description: |-
   Diff::LCS computes the difference between two Enumerable sequences using the
   McIlroy-Hunt longest common subsequence (LCS) algorithm. It includes utilities
   to create a simple HTML diff output format and a standard diff-like tool.
 
   This is release 1.4.3, providing a simple extension that allows for
-  Diff::LCS::Change objects to be treated implicitly as arrays and fixes a
-  number of formatting issues.
+  Diff::LCS::Change objects to be treated implicitly as arrays and fixes a number
+  of formatting issues.
 
-  Ruby versions below 2.5 are soft-deprecated, which means that older versions
-  are no longer part of the CI test suite. If any changes have been introduced
-  that break those versions, bug reports and patches will be accepted, but it
-  will be up to the reporter to verify any fixes prior to release. The next
-  major release will completely break compatibility.
+  Ruby versions below 2.5 are soft-deprecated, which means that older versions are
+  no longer part of the CI test suite. If any changes have been introduced that
+  break those versions, bug reports and patches will be accepted, but it will be
+  up to the reporter to verify any fixes prior to release. The next major release
+  will completely break compatibility.
 email:
 - halostatue@gmail.com
 executables:
@@ -161,23 +181,29 @@ executables:
 - ldiff
 extensions: []
 extra_rdoc_files:
-- Code-of-Conduct.md
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- CONTRIBUTING.md
+- CONTRIBUTORS.md
 - Contributing.md
-- History.md
-- License.md
+- LICENCE.md
 - Manifest.txt
-- README.rdoc
+- README.md
+- SECURITY.md
 - docs/COPYING.txt
 - docs/artistic.txt
 files:
 - ".rspec"
-- Code-of-Conduct.md
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- CONTRIBUTING.md
+- CONTRIBUTORS.md
 - Contributing.md
-- History.md
-- License.md
+- LICENCE.md
 - Manifest.txt
-- README.rdoc
+- README.md
 - Rakefile
+- SECURITY.md
 - bin/htmldiff
 - bin/ldiff
 - docs/COPYING.txt
@@ -232,16 +258,15 @@ files:
 homepage: https://github.com/halostatue/diff-lcs
 licenses:
 - MIT
-- Artistic-2.0
-- GPL-2.0+
+- Artistic-1.0-Perl
+- GPL-2.0-or-later
 metadata:
-  homepage_uri: https://github.com/halostatue/diff-lcs
-  source_code_uri: https://github.com/halostatue/diff-lcs
-  bug_tracker_uri: https://github.com/halostatue/diff-lcs/issues
+  rubygems_mfa_required: 'true'
+  changelog_uri: https://github.com/halostatue/diff-lcs/blob/main/CHANGELOG.md
 post_install_message:
 rdoc_options:
 - "--main"
-- README.rdoc
+- README.md
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
@@ -255,7 +280,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.6
+rubygems_version: 3.5.22
 signing_key:
 specification_version: 4
 summary: Diff::LCS computes the difference between two Enumerable sequences using

data/Code-of-Conduct.md

@@ -1,74 +0,0 @@
-# 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, gender identity and expression, level of experience,
-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 [INSERT EMAIL ADDRESS]. 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 [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/