minitest-sequel 0.3.1 → 0.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 32911aa9b36b9feffbd951deaab43c5ae347d977
-  data.tar.gz: bfad7703475b916ceff9e11830a3776ff7f0eab9
+SHA256:
+  metadata.gz: c3264c6433380c988f31f93d66cdb8f45ee1462cf398fcabd1d5b6e5f04c5104
+  data.tar.gz: cb9c428a9eefc588c2467450378afda44f9e1bbec3960a96531be398355c07b9
 SHA512:
-  metadata.gz: c18133741f9efcdd2d697db4ccc6e8e33395ab3e1cb69224bd6e5845469a3e5be0ffdc0f3e5de728276d0e68b30ea1186f189c868e7cc7fd04a92aab12226a40
-  data.tar.gz: 6412a53447e6244be2ef4baf4acf8ae6455a2c5016961078cea61e89429dfcee2e2021b535eda532ddfda871cafa50648af2cfef434b6fec0e202c6362d21e8c
+  metadata.gz: 881f6ace636163bffd8026fcbc5502c9ca4a4ed28cfc97a8acfcc1af4370fafc01ee28455d20aa4edb419e533ff87f3933b0a5af4ac6e97599df7bf14c8d86f3
+  data.tar.gz: 5a04be3b799848daa8e308dde6aa91f6cda085127ce80b7ce18c141fb4abaff6ece95615c4e1c9246136412966c366180fe8266b40823c8e74b5fd25b2c7100d

data/.github/dependabot.yml

@@ -0,0 +1,24 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "saturday"
+      time: "21:45"
+      timezone: Asia/Kuala_Lumpur
+  - package-ecosystem: "bundler" # See documentation for possible values
+    directory: "/" # Location of package manifests
+    groups:
+      patch-and-minor-dependencies:
+        update-types: ["patch", "minor"]
+    schedule:
+      interval: "weekly"
+      day: "saturday"
+      time: "21:45"
+      timezone: Asia/Kuala_Lumpur

data/.github/workflows/ruby.yml

@@ -0,0 +1,45 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+# GitHub recommends pinning actions to a commit SHA.
+# To get a newer version, you will need to update the SHA.
+# You can also reference a tag or branch, but the action may change without warning.
+
+name: Ruby
+
+on:
+  push:
+    branches: ["master", "ruby-v3x"]
+  pull_request:
+    branches: ["master", "ruby-v3x"]
+
+permissions:
+  contents: read
+
+jobs:
+  lint_and_test:
+    env:
+      RACK_ENV: test
+      COVERAGE: "true"
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        ruby-version: ["3.0", "3.1", "3.2", "3.3"]
+        # Disable JRuby for now
+        # ruby-version: ["3.0", "3.1", "3.2", "3.3", "jruby-9.4"]
+    runs-on: ${{ matrix.os }}
+    timeout-minutes: 3
+
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up Ruby
+        # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
+        # change this to (see https://github.com/ruby/setup-ruby#versioning):
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby-version }}
+          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
+      - name: Run rake (lint and test)
+        run: bundle exec rake

data/.gitignore

@@ -9,3 +9,4 @@
 /tmp/
 /rubocop/
 /.vscode
+NOTES.md

data/.rubocop.yml

@@ -0,0 +1,48 @@
+inherit_from: .rubocop_todo.yml
+
+require:
+  - rubocop-minitest
+  - rubocop-performance
+  - rubocop-rake
+
+# The behavior of RuboCop can be controlled via the .rubocop.yml
+# configuration file. It makes it possible to enable/disable
+# certain cops (checks) and to alter their behavior if they accept
+# any parameters. The file can be placed either in your home
+# directory or in some project directory.
+#
+# RuboCop will start looking for the configuration file in the directory
+# where the inspected file is and continue its way up to the root directory.
+#
+# See https://docs.rubocop.org/rubocop/configuration
+
+AllCops:
+  TargetRubyVersion: "3.0"
+  NewCops: enable
+
+Metrics/BlockLength:
+  Enabled: true
+  Exclude:
+    - "spec/**/*.rb"
+    - "**/*.gemspec"
+
+Metrics/ModuleLength:
+  Enabled: true
+  Exclude:
+    - "lib/minitest/sequel/validations.rb"
+
+Style/Documentation:
+  Exclude:
+    - "spec/**/*"
+    - "test/**/*"
+
+Style/RegexpLiteral:
+  Enabled: true
+  EnforcedStyle: slashes
+  # AllowInnerSlashes: false
+
+Layout/LineLength:
+  Enabled: true
+  Max: 100
+  Exclude:
+    - "**/*.gemspec"

data/.rubocop_todo.yml

@@ -0,0 +1,7 @@
+# This configuration was generated by
+# `rubocop --auto-gen-config`
+# on 2024-10-07 15:17:42 UTC using RuboCop version 1.66.1.
+# The point is for the user to remove these configuration records
+# one by one as the offenses are removed from the code base.
+# Note that changes in the inspected code, or installation of new
+# versions of RuboCop, may require this file to be generated again.

data/CODE_OF_CONDUCT.md

@@ -1,20 +1,27 @@
 # Contributor Code of Conduct
 
-As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting  issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
+As contributors and maintainers of this project, we pledge to respect all people
+who contribute through reporting  issues, posting feature requests, updating
+documentation, submitting pull requests or patches, and other activities.
 
-We are committed to making participation in this project a harassment-free experience for everyone, regardless of 
-level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, 
+We are committed to making participation in this project a harassment-free
+experience for everyone, regardless of level of experience, gender, gender
+identity and expression, sexual orientation, disability, personal appearance,
 body size, race, ethnicity, age, or religion.
 
-Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory 
-comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
+Examples of unacceptable behavior by participants include the use of sexual
+language or imagery, derogatory comments or personal attacks, trolling, public
+or private harassment, insults, or other unprofessional conduct.
 
-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. Project maintainers who do not 
+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. Project maintainers who do not
 follow the Code of Conduct may be removed from the project team.
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or 
-contacting one or more of the project maintainers.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by opening an issue or contacting one or more of the project
+maintainers.
 
-This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.0.0, 
+This Code of Conduct is adapted from the
+[Contributor Covenant](http://contributor-covenant.org), version 1.0.0,
 available at [http://contributor-covenant.org/version/1/0/0/](http://contributor-covenant.org/version/1/0/0/)

data/Gemfile

@@ -1,4 +1,83 @@
-source "https://rubygems.org"
+# frozen_string_literal: true
 
-# Specify your gem's dependencies in minitest-sequel.gemspec
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in minitest-have_tag.gemspec
 gemspec
+
+# adding these to silence warnings for Ruby v3.5
+gem 'fiddle'
+gem 'logger'
+gem 'ostruct'
+
+group :development do
+  # A command line tool to easily handle events on file system modifications
+  # DOCS: https://github.com/guard/guard
+  gem 'guard'
+  # automatically runs your tests with Minitest framework
+  # DOCS: https://github.com/guard/guard-minitest
+  gem 'guard-minitest'
+
+  # Ruby testing framework
+  # DOCS: https://github.com/seattlerb/minitest
+  gem 'minitest', '~> 5.7', '>= 5.7.0'
+  # Adds specific assertions for testing exceptions with minitest
+  # DOCS: https://github.com/kematzy/minitest-assert_errors
+  gem 'minitest-assert_errors'
+  # Around and before_all/after_all hooks for Minitest
+  # DOCS: https://github.com/jeremyevans/minitest-hooks
+  gem 'minitest-hooks', '~> 1.1', '>= 1.1.0'
+  # Colored red/green output for Minitest
+  # DOCS: https://github.com/blowmage/minitest-rg
+  gem 'minitest-rg', '~> 5.3', '>= 5.3.0'
+
+  # Ruby build program with capabilities similar to Make
+  # DOCS: https://github.com/ruby/rake
+  gem 'rake', '~> 13.0'
+
+  # Ruby static code analyzer and formatter
+  # DOCS: https://github.com/rubocop/rubocop
+  gem 'rubocop', '~> 1.31', require: false
+  # Code style checking for Minitest files
+  # DOCS: https://github.com/rubocop/rubocop-minitest
+  gem 'rubocop-minitest', require: false
+  # Performance optimization analysis for your projects
+  # DOCS: https://github.com/rubocop/rubocop-performance
+  gem 'rubocop-performance', require: false
+  # A RuboCop extension focused on enforcing Rake best practices and coding conventions
+  # DOCS: https://github.com/rubocop/rubocop-rake
+  gem 'rubocop-rake', require: false
+
+  # SQLite3 interface for Ruby
+  # DOCS: https://github.com/sparklemotion/sqlite3-ruby
+  gem 'sqlite3'
+
+  # Code coverage for Ruby
+  # DOCS: https://github.com/simplecov-ruby/simplecov
+  gem 'simplecov'
+
+  # A Ruby language server that provides intellisense, code completion, and inline documentation
+  # DOCS: https://github.com/castwide/solargraph
+  gem 'solargraph'
+end
+
+# Linux-specific gems
+install_if -> { RUBY_PLATFORM.include?('linux') } do
+  # Linux inotify wrapper for Ruby
+  # DOCS: https://github.com/guard/rb-inotify
+  gem 'rb-inotify', require: false
+end
+
+# macOS-specific gems
+install_if -> { RUBY_PLATFORM.include?('darwin') } do
+  # FSEvents API with signals handled for macOS
+  # DOCS: https://github.com/thibaudgg/rb-fsevent
+  gem 'rb-fsevent', require: false
+end
+
+# Windows-specific gems
+install_if -> { Gem.win_platform? } do
+  # Windows Directory Monitor - A library which can be used to monitor directories for changes
+  # DOCS: https://github.com/Maher4Ever/wdm
+  gem 'wdm'
+end

data/Guardfile

@@ -0,0 +1,26 @@
+# frozen_string_literal: true
+
+# A sample Guardfile
+# More info at https://github.com/guard/guard#readme
+
+## Uncomment and set this to only include directories you want to watch
+# directories %w(app lib config test spec features) \
+#  .select{|d| Dir.exist?(d) ? d : UI.warning("Directory #{d} does not exist")}
+
+## Note: if you are using the `directories` clause above and you are not
+## watching the project directory ('.'), then you will want to move
+## the Guardfile to a watched dir and symlink it back, e.g.
+#
+#  $ mkdir config
+#  $ mv Guardfile config/
+#  $ ln -s config/Guardfile .
+#
+# and, you'll have to watch "config/Guardfile" instead of "Guardfile"
+
+guard :minitest do
+  # with Minitest::Spec
+  watch(%r{^spec/(.*)_spec\.rb$})
+  watch(%r{^lib/minitest/sequel/(.+)\.rb$}) { 'spec' }
+  # watch(%r{^lib/(.+)\.rb$})               { |m| "spec/#{m[1]}_spec.rb" }
+  watch(%r{^spec/spec_helper\.rb$})         { 'spec' }
+end