Default config.enabled_environments to nil instead of []

[sl0thentr0py]

Issues

• resolves Sentry reports traces and errors even if enabled_environments is empty #2611
• resolves RUBY-68

[linear]

RUBY-68 Sentry reports traces and errors even if enabled_environments is empty

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.41%. Comparing base (ed7a2db) to head (07d8d87).
⚠️ Report is 1 commits behind head on 6.0-dev.

Additional details and impacted files

@@             Coverage Diff             @@
##           6.0-dev    #2716      +/-   ##
===========================================
+ Coverage    95.83%   97.41%   +1.58%     
===========================================
  Files          141      143       +2     
  Lines         5494     5606     +112     
===========================================
+ Hits          5265     5461     +196     
+ Misses         229      145      -84     

Components	Coverage Δ
sentry-ruby	97.69% <100.00%> (+0.47%)	⬆️
sentry-rails	96.59% <ø> (+8.32%)	⬆️
sentry-sidekiq	96.57% <ø> (ø)
sentry-resque	94.44% <ø> (ø)
sentry-delayed_job	94.68% <ø> (-0.98%)	⬇️
sentry-opentelemetry	99.31% <ø> (ø)

Files with missing lines	Coverage Δ
sentry-ruby/lib/sentry/configuration.rb	98.40% <100.00%> (ø)
sentry-ruby/lib/sentry/test_helper.rb	96.15% <100.00%> (+0.07%)	⬆️

... and 47 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[solnic]

Just a remark for now but eventually it would be good to have a more explicit interface for checking if a setting is disabled, something like config.enabled?(:enabled_environments) or something like this, because nil checks are bug prone.