Rails debugging - byebug starts on production environment

[ey123]

If I forget a "byebug" command in the code and it gets deployed to production, byebug stops on the breakpoint.

When I used debugger gem it used to skip "debugger" commands.
I tried Byebug.stop() in config/environments/production.rb - didn't work.

Is there any way I can make byebug disabled for production?

Thanks.

[deivid-rodriguez]

Thanks for the report. What was exactly previous debugger behaviour. It ignored it but gave you a warning message or something?

The truth is I don't feel like spending time now on babysitting developers. Maybe you can override byebug's method and check for the environment there...

Salute.

[michaelglass]

👍 def not a byebug issue

[keichan34]

I usually put byebug in the Gemfile under the :development group, so it's not even loaded in production or staging. That way, it'll throw a NoMethodError and you'll (hopefully) catch it on your staging environment.

[deivid-rodriguez]

I'm closing this because I didn't get any feedback and because I don't think this is byebug's issue

[deivid-rodriguez]

@ey123 Funny enough, just today support for byebug forgotten calls was added to rubocop (see rubocop/rubocop#969) so it seems that this issue should be definitely closed. :)

[Alphabetus]

The truth is I don't feel like spending time now on babysitting developers. Maybe you can override byebug's method and check for the environment there...

Just came here to point the magnificent reply you posted here.
I have no words for that comment. You must be a true gent.