[BUG] Seems to break "binding.pry" about ruby_jard HOT 4 CLOSED

Hi @kikonen, thanks for reporting. This issue is mentioned in #39, and already fixed in #41. Unfortunately, I haven't release a new version yet. So, in the meantime, you can install the gem pointing directly to this repo's master branch.

gem 'ruby_jard', group: :development, git: 'https://github.com/nguyenquangminh0711/ruby_jard'

I'll comment in this issue when the patched version is released.

from ruby_jard.

yes, that problem is seemingly fixed there

from ruby_jard.

Nope, actually doesn't work always

howto

• "jard" breakpoint in line
• execute action in rails app
• hit breakpoint and continue
• replace breakpoint to be "binding.pry"
• execute action in rails app
  => "jard_control_flow" error hit

And seemingly after this is hit, have to force exit pry session via "!!!" and then kill and restart rails server

from ruby_jard.

@kikonen Yeah, that's kinda a limitation. I mentioned in one of the issue links above:

The limitation is that after jard is first triggered, the backward compatibility is not guranteed anymore. The reason is that after Jard starts, it takes over internal states of Pry and Byebug. So, byebug and pry are not awared of external changes, and won't work as expected. If Jard doesn't start, they are fine.

When you do a live-reloading, the reloading engine replaces the content of the file you injected, Jard configuration stays intact. So, when binding.pry is triggered with Jard-specific configurations. Overcoming this limitation is not possible now. Both Byebug and Pry somehow depends on the global configurations. In further future, I may make some contributions to them to fix this issue forever.

from ruby_jard.