Reasoning for on_exception hook not triggering in local env?

Jets
1

According to http://rubyonjets.com/docs/jets-turbines the on_exception hook isn’t triggered in the local environment.

I’m curious as to the reasoning behind this?

IMO it would be preferable to have identical behaviour of on_exception locally to avoid breaking principle of least surprise. I would rather disable exception handling services 12factor style via ENV vars. E.g for Rollbar:

Rollbar.configure do |config|
  config.enabled = ENV["ROLLBAR_ACCESS_TOKEN"].present?
end
2

Main reason is that the code logic doesn’t go through the Ruby shim locally but only remotely on Lambda. Adding the on_exception at the common shim point was a quick way to add the feature.

Yup. Would be nice if it triggered locally also. It’s some more work but am happy to consider PRs :ok_hand: