solid_callback 3.0.0 → 3.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fff26382f82c48f8ffdc91046c65e8f33dba192b17463a00a44a720325b4561f
-  data.tar.gz: 428d700ce0867f8be0ee11e9219b5ca7ac2da3ba0dddbc3d006e92a9c6ad4f8b
+  metadata.gz: 8d4868400ada59602777596c75942cdb942d5be9e44ad383d766706ce1bc14b0
+  data.tar.gz: 8131d95e2f3c04527216b38c4a030bfcb9e623e6b1912e344fa7fa592237aee0
 SHA512:
-  metadata.gz: 755e70d9004ad6cfc06bd23286864f56ebf2c4d43ffe969751ad9eb52cb29d848c26113f78e4d07ddb52ab1b96e4946fdb21ec003037e09f3161a53abacb4872
-  data.tar.gz: 338864ffd6ac8ee32f9b4e5576ff80a7d8c31e59ae420ccabf3600996766c6aa5b9c2c060d3e9446a46bbe1b123b1bcd414a44fee2c0a57aea846c0bfe8723ad
+  metadata.gz: 11fd8d6357fe2b71c683443f03bb0db6eb45a7467cf048ea5a0a30b06aee63f4a75329cbc39220524828cf596b871c1bdcba781b264bc646f7fa64899cb8818c
+  data.tar.gz: 7373f5b5c012a02d8cd6c4dbde06bf25e5bac6ad35591f4e3043245a03dd4b0043f5c201ced775864838d56426b6cd76af56b483996f8320677ba3b2da9b96cd

data/README.md

@@ -2,7 +2,7 @@
 
 [![Gem Version](https://badge.fury.io/rb/solid_callback.svg?icon=si%3Arubygems)](https://badge.fury.io/rb/solid_callback)
 [![Test](https://github.com/gklsan/solid_callback/actions/workflows/ruby.yml/badge.svg)](https://github.com/gklsan/solid_callback/actions/workflows/ruby.yml)
-[![Downloads](https://img.shields.io/gem/dt/simple_http_service.svg)](https://badge.fury.io/rb/simple_http_service)
+[![Downloads](https://img.shields.io/gem/dt/solid_callback.svg)](https://badge.fury.io/rb/solid_callback)
 [![Github forks](https://img.shields.io/github/forks/gklsan/solid_callback.svg)](https://github.com/gklsan/solid_callback/network)
 [![Github stars](https://img.shields.io/github/stars/gklsan/solid_callback.svg)](https://github.com/gklsan/solid_callback/stargazers)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
@@ -18,6 +18,10 @@ SolidCallback adds powerful method interception capabilities to your Ruby classe
 - 🔒 **Thread-safe**: Safely use in concurrent applications
 - 📝 **Conditional execution**: Run callbacks only when specific conditions are met
 
+## Requirements
+
+- Ruby >= 3.3.0
+
 ## Installation
 
 Add this line to your application's Gemfile:
@@ -138,15 +142,13 @@ before_call :notify_admin, if: -> { Rails.env.production? }
 
 ### Skipping Callbacks
 
-Skip callbacks for specific methods:
+Use `except:` to exclude specific methods from a callback:
 
 ```ruby
 class ApiService
   include SolidCallback
   
-  before_call :rate_limit
-  
-  skip_callbacks_for :health_check
+  before_call :rate_limit, except: [:health_check]
   
   def get_data
     # Implementation...
@@ -159,6 +161,10 @@ class ApiService
 end
 ```
 
+> **Note:** `skip_callbacks_for` is also available on the class, but it currently only
+> records the given method names — it does not yet suppress callback execution. Prefer
+> `except:` (as above) until that's wired up.
+
 ## Callback Options
 
 Each callback method accepts the following options:
@@ -172,12 +178,24 @@ Each callback method accepts the following options:
 
 ## How It Works
 
-Callbacker uses Ruby's metaprogramming to wrap your methods with callback functionality:
-
-1. When included, it extends your class with callback registration methods
-2. When a callback is registered, it stores the configuration
-3. When a method is defined, it wraps the method with callback handling code
-4. When the method is called, it executes the callbacks in the proper order
+SolidCallback uses Ruby's metaprogramming to wrap your methods with callback functionality:
+
+1. `include SolidCallback` extends your class with the callback registration API and
+   hooks into `method_added` so newly defined methods can be wrapped automatically.
+2. `before_call`, `after_call`, and `around_call` just store the callback configuration
+   (method name, `only`/`except`/`if`/`unless`) on the class — they don't need to run
+   before the target method is defined.
+3. Each time a **public** instance method is defined, it's aliased to
+   `_solid_callback_original_<method>` and replaced with a wrapper that runs the
+   applicable `before` callbacks, then the `around` chain (which ultimately calls the
+   original method), then the applicable `after` callbacks. Private/protected methods
+   are left untouched.
+4. Applicability (`only`, `except`, `if`, `unless`) is evaluated per call, against the
+   actual instance, so the same callback can behave differently per invocation.
+5. `around_call` callbacks are nested in registration order (the first one registered is
+   outermost) and must `yield` to continue the chain, much like Rack middleware.
+6. If a method needs wrapping outside the normal `method_added` flow, call
+   `wrap_methods(:method_name, ...)` explicitly.
 
 ## 📚 Use Cases
 

data/lib/solid_callback/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module SolidCallback
-  VERSION = "3.0.0"
+  VERSION = "3.1.0"
 end

data/mise.toml

@@ -1,2 +1,2 @@
 [tools]
-ruby = "4"
+ruby = "3.4.2"

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: solid_callback
 version: !ruby/object:Gem::Version
-  version: 3.0.0
+  version: 3.1.0
 platform: ruby
 authors:
 - Gokul (gklsan)
 bindir: exe
 cert_chain: []
-date: 1980-01-02 00:00:00.000000000 Z
+date: 2026-07-07 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -124,14 +124,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 4.0.1
+      version: 3.3.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.3
+rubygems_version: 3.6.6
 specification_version: 4
 summary: SolidCallback adds powerful method interception capabilities to your Ruby
   classes with near-zero overhead. Clean, flexible, and unobtrusive.