[corsonknowles]

Summary

This adds lib/dogstatsd/ruby.rb, a one-line convenience entrypoint so Bundler.require loads the gem from a plain gem 'dogstatsd-ruby' Gemfile line. require 'datadog/statsd' stays the documented require path, and nothing about it changes.

Why

Bundler's autorequire first tries require 'dogstatsd-ruby'. When that raises a LoadError for exactly that path and the name contains dashes, it retries with every - replaced by /, i.e. require 'dogstatsd/ruby'. If that also fails, Bundler skips the gem without a warning.

Neither path exists today, so in an app that relies on Bundler.require (Rails does by default), Datadog::Statsd is only defined if something else requires datadog/statsd. To get it loaded, consumers currently have to write gem 'dogstatsd-ruby', require: 'datadog/statsd' or add a manual require.

Change

lib/dogstatsd/ruby.rb contains only:

# frozen_string_literal: true

require_relative '../datadog/statsd'

• Purely additive and backward compatible. It adds no new constants, and requiring both paths loads the code once.
• It ships automatically, because s.files already includes lib/**/*.rb.
• I didn't touch the CHANGELOG or the version, since both look like they're updated at release time.

Verification

$ ruby -Ilib -e "require 'dogstatsd/ruby'; p defined?(Datadog::Statsd); p Datadog::Statsd::VERSION"
"constant"
"5.7.1"

I tested Bundler.require with installed gems in an isolated BUNDLE_PATH, using a Gemfile containing only gem 'dogstatsd-ruby', '5.7.1' with no require:, then Bundler.require; p defined?(Datadog::Statsd):

• released 5.7.1 from rubygems.org: nil
• gem built from this branch: "constant"

(A path: Gemfile is no good for the "before" case. Evaluating the gemspec requires lib/datadog/statsd/version.rb, which loads enough of the library to define Datadog::Statsd before Bundler.require even runs.)

rubocop lib/dogstatsd/ruby.rb reports no offenses.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-27T23:13:29.974929Z	9862bca	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.