roda-tags 0.1.2 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bbb664e3631e6d39aa3212dfbd9eb961b37119be6aff06e9a3f8961c2016f439
-  data.tar.gz: 4390edc0fbfb6345a010b3a708610c9ee7503e7a7c3f9cde4eb948dbd9a3ee07
+  metadata.gz: aa178f86ef46ab232994a1dfd3c258af3e17b0c4fea89306f0ea25a13da0b0df
+  data.tar.gz: 85182aa12331f7cf769118b18559e5c2c6163df4bb174c29faf3eb49639515fd
 SHA512:
-  metadata.gz: f2bb71d4b8aa4118d8c704b757cb6da809887367dffb5325a374ba877a67e4007db8347cc331ffc533a80db30769243b265c2dd83b59c532e51d185f1806520c
-  data.tar.gz: 14b7b2856e657ddd81c999397bf06a980a2a4d937c8c48c3be2bdd69a9285e426a879d105a298c63a44197f73294d5913f7888681ee4e91415019ac0311e31df
+  metadata.gz: 1520651d453044cc24d6755621befd207294ce41f682c27b93b53df7a56d46ab83a5d0e8a1a71e4559695770cdef5050c3814d8ebf160ce50c222776b92c3bbb
+  data.tar.gz: 9c64e4afc3c3cae26a1a58091576ca22130429133decaf808d83907238404c56b0c10e9f9a2115df51df1e042de95910a6637195fe96121edb2fce316c553e14

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:30"
+      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:30"
+      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

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

data/.rubocop.yml

@@ -0,0 +1,33 @@
+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
+
+Style/StringLiterals:
+  EnforcedStyle: single_quotes
+
+Style/StringLiteralsInInterpolation:
+  EnforcedStyle: double_quotes
+
+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-11-11 09:26:46 UTC using RuboCop version 1.68.0.
+# 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,24 +1,30 @@
 # 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, body size, race, ethnicity, age, or religion.
+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 follow the Code of Conduct may be removed from the project team.
+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.
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an 
-issue or contacting one or more of the project maintainers.
+Project maintainers who do not follow the Code of Conduct may be removed from
+the project team.
 
-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/)
+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,
+available at [http://contributor-covenant.org/version/1/0/0/](http://contributor-covenant.org/version/1/0/0/)

data/Gemfile

@@ -1,4 +1,90 @@
+# frozen_string_literal: true
+
 source 'https://rubygems.org'
 
 # Specify your gem's dependencies in roda-tags.gemspec
 gemspec
+
+# adding these to silence warnings for Ruby v3.5
+gem 'base64'
+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'
+  # Minitest assertions testing HTML tags
+  # DOCS: https://github.com/kematzy/minitest-have_tag
+  gem 'minitest-have_tag', '~> 0.2.1', '>= 0.2.0'
+  # 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 HTML/XML parser and document traversal helper
+  # DOCS: https://github.com/sparklemotion/nokogiri
+  gem 'nokogiri', '~> 1.16.7', '>= 1.16.0'
+  # Simple testing API for Rack based applications
+  # DOCS: https://github.com/rack/rack-test
+  gem 'rack-session', '~> 2.0.0', '>= 2.0.0'
+  # Simple testing API for Rack based applications
+  # DOCS: https://github.com/rack/rack-test
+  gem 'rack-test', '~> 2.1.0', '>= 2.1.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
+
+  # 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,25 @@
+# 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/(.+)\.rb$})         { 'spec' }
+  watch(%r{^spec/spec_helper\.rb$}) { 'spec' }
+end