configuration.rb in sentry-rails-5.17.0

- old
+ new

@@ -102,11 +102,11 @@
       "service_delete_prefixed.active_storage" => %i[service prefix],
       "service_exist.active_storage" => %i[service key exist],
       "service_url.active_storage" => %i[service key url],
       "service_update_metadata.active_storage" => %i[service key],
       "preview.active_storage" => %i[key],
-      "analyze.active_storage" => %i[analyzer],
+      "analyze.active_storage" => %i[analyzer]
     }.freeze
 
     class Configuration
       # Rails 7.0 introduced a new error reporter feature, which the SDK once opted-in by default.
       # But after receiving multiple issue reports, the integration seemed to cause serious troubles to some users.
@@ -114,11 +114,11 @@
       # More information can be found from: https://github.com/rails/rails/pull/43625#issuecomment-1072514175
       attr_accessor :register_error_subscriber
 
       # Rails catches exceptions in the ActionDispatch::ShowExceptions or
       # ActionDispatch::DebugExceptions middlewares, depending on the environment.
-      # When `rails_report_rescued_exceptions` is true (it is by default), Sentry
-      # will report exceptions even when they are rescued by these middlewares.
+      # When `report_rescued_exceptions` is true (it is by default), Sentry will
+      # report exceptions even when they are rescued by these middlewares.
       attr_accessor :report_rescued_exceptions
 
       # Some adapters, like sidekiq, already have their own sentry integration.
       # In those cases, we should skip ActiveJob's reporting to avoid duplicated reports.
       attr_accessor :skippable_job_adapters