quonfig 0.0.5 → 0.0.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: eb6a88a2132fd0fe54fc656ffe1b81916e4487258c2a54dd5589d0bb56b1e300
-  data.tar.gz: e91e3cce0cc73793e2c0c1fb407192cbd5a8caad9c96bfbfae6d6bf2fa69ea78
+  metadata.gz: 875b035905394220e72fec4fc1afc3bc62ad6e2975b745098fa4482e1dc348d0
+  data.tar.gz: bd957d0ec077f3a49daf719deb3ea4db64d1b23a69f6264c91385ad21ff06720
 SHA512:
-  metadata.gz: d33195dcf4fd9b52f8e245e102fbf21a405626aaa8e1157294a79c83cb8a1f91b78249782a9b7318728f31d342adc9f4565d082886d041d53a44995f8adfcb45
-  data.tar.gz: fa6b7dd2497f9d202e985619ccccf754162b538c1cd7ffc41d0c7f6679e83d55ac1739d3ed1dc76931b7a9a14be1db9e5f35514a9ff86c9997feecda9342159d
+  metadata.gz: 9a592d367c361e42e57c42b0ca0929927808e834b5f876545e17436403b11eb5abe08d2996317e5ec5360a1df2228b48a247e22304d6fcda809c3ffee0e3f772
+  data.tar.gz: f3f9b9b1135ab775861164fb89701e6a3cf6b5cb23078d55de89604b13081ce71b7fe00bed192cd9d9134d64fd406fec954efa793e62a2fb558a8ca3cddbec4f

data/CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog
 
+## 0.0.6 - 2026-04-22
+
+- **New: `Quonfig::StdlibFormatter` + `client.stdlib_formatter(logger_name:)`** —
+  Ruby's built-in `::Logger` now gets drop-in dynamic log-level gating,
+  on par with the existing SemanticLogger integration. The client helper
+  returns a Proc matching the stdlib `logger.formatter =` contract
+  (`(severity, datetime, progname, msg) -> String`). For each log call
+  the proc evaluates `should_log?(logger_path: logger_name || progname,
+  desired_level: severity)` and either formats the record or returns an
+  empty string (which `::Logger` writes as zero bytes, suppressing the
+  line). `logger_name` flows into `quonfig-sdk-logging.key` verbatim —
+  no normalization — so customer rules target exact class names.
+  Raises `Quonfig::Error` if `logger_key` was not set at init. Parallels
+  sdk-node's Winston formatter, sdk-python's `logging.Filter`, and
+  sdk-go's `slog.Handler`. Closes Stage 2 of the per-SDK logger-path
+  rollout.
+
 ## 0.0.5 - 2026-04-22
 
 - **BREAKING — SemanticLoggerFilter context key renamed.** The filter

data/README.md

@@ -203,6 +203,42 @@ Pass `key_prefix:` to use a prefix other than `log-levels.`:
 client.semantic_logger_filter(key_prefix: 'debug.')
 ```
 
+## Dynamic log levels with stdlib Logger
+
+If you use Ruby's built-in `::Logger` instead of SemanticLogger, wire the
+formatter returned by `client.stdlib_formatter` into your logger:
+
+```ruby
+require 'quonfig'
+require 'logger'
+
+client = Quonfig::Client.new(
+  sdk_key:    ENV['QUONFIG_BACKEND_SDK_KEY'],
+  logger_key: 'log-level.my-app'
+)
+
+logger = ::Logger.new($stdout)
+logger.level = ::Logger::DEBUG
+logger.formatter = client.stdlib_formatter(logger_name: 'MyApp::Services::Auth')
+```
+
+The formatter asks the client `should_log?(logger_path:, desired_level:)`
+for every call; lines below the configured level return an empty string
+(which `::Logger` writes as zero bytes, suppressing the line). `logger_name`
+is passed to Quonfig verbatim under `quonfig-sdk-logging.key` so a single
+`log-level.my-app` config can drive per-class overrides via rules like
+`PROP_STARTS_WITH_ONE_OF "MyApp::Services::"`.
+
+Omit `logger_name:` to have the formatter fall through to the Logger's
+`progname` at call time:
+
+```ruby
+logger.formatter = client.stdlib_formatter
+logger.progname  = 'MyApp::Services::Auth'
+```
+
+If both are supplied, the explicit `logger_name:` wins.
+
 ## Documentation
 
 Full documentation, including SPEC, SDK reference, and operational guides, is

data/VERSION

@@ -1 +1 @@
-0.0.5
+0.0.6

data/lib/quonfig/client.rb

@@ -125,6 +125,29 @@ module Quonfig
         Quonfig::SemanticLoggerFilter.new(self, config_key: config_key)
     end
 
+    # Build a formatter Proc for Ruby's built-in +::Logger+. The returned
+    # proc honors dynamic log levels from the client's +logger_key+ config:
+    # for each log call, it evaluates +should_log?+ and either formats the
+    # record or returns an empty string (suppressing output).
+    #
+    # Matches ReforgeHQ's +stdlib_formatter+ API name (snake_case).
+    #
+    # Usage:
+    #   logger = ::Logger.new($stdout)
+    #   logger.formatter = client.stdlib_formatter                       # uses progname
+    #   logger.formatter = client.stdlib_formatter(logger_name: 'MyApp') # fixed name
+    #
+    # Raises +Quonfig::Error+ if +logger_key+ was not set at init — parallels
+    # +should_log?+'s behavior.
+    #
+    # @param logger_name [String, nil] fallback logger identifier used when
+    #   +progname+ isn't supplied by the Logger call site. If both are
+    #   present, +logger_name+ wins.
+    # @return [Proc] a +(severity, datetime, progname, msg) -> String+ proc.
+    def stdlib_formatter(logger_name: nil)
+      Quonfig::StdlibFormatter.build(self, logger_name: logger_name)
+    end
+
     # The configured +logger_key+ from Options — the Quonfig config key the
     # higher-level +should_log?+ helper evaluates per-logger. +nil+ if the
     # client was not configured for dynamic log levels.

data/lib/quonfig.rb

@@ -51,6 +51,7 @@ require 'quonfig/context'
 require 'quonfig/client'
 require 'quonfig/bound_client'
 require 'quonfig/semantic_logger_filter'
+require 'quonfig/stdlib_formatter'
 require 'quonfig/quonfig'
 require 'quonfig/murmer3'
 require 'quonfig/semver'

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: quonfig
 version: !ruby/object:Gem::Version
-  version: 0.0.5
+  version: 0.0.6
 platform: ruby
 authors:
 - Jeff Dwyer