You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you want to debug Packwerk for a specific context (file + constant), it's quite difficult to do without running a debugger for all contexts. What if we dropped into a debugger whenever we see an AST node that is a call, for a method named debugger, and no arguments?
These are generally not found in code that gets committed, so it should be non-intrusive, but best to scope it behind a flag/subcommand to be safe.
The text was updated successfully, but these errors were encountered:
When you want to debug Packwerk for a specific context (file + constant), it's quite difficult to do without running a debugger for all contexts. What if we dropped into a debugger whenever we see an AST node that is a call, for a method named debugger, and no arguments?
These are generally not found in code that gets committed, so it should be non-intrusive, but best to scope it behind a flag/subcommand to be safe.
The text was updated successfully, but these errors were encountered: