-
Notifications
You must be signed in to change notification settings - Fork 153
catch pry breakpoints #36
Comments
Great idea. We'd want to check for either of these two lines in any *.rb file - libraries, recipes, lwrp's... Do you use pry from within template code (erubis)? |
I have not tried it in an erubis template but I will eventually. No idea whether or not it works in erubis templates |
It should be possible to use pry within code blocks in a template in which case the rule could check for this as well - I don't know if people are actually doing this though in normal usage. Separately you've made me think that a rule to look for naming inconsistencies between the variables passed into a template versus those used in the template would be a useful addition too. |
Hi Bryan, I've added a new rule FC030 to master for this. Can you give it a try and let me know if it works for you. Cheers, Andrew. |
will try to test it out today, tks On Sun, Jun 3, 2012 at 11:05 PM, Andrew Crump <
|
works nicely! tks to the Crumpster! Everyone's favorite iguana :) |
I don't know what that means. I hereby challenge you to a dance battle: |
pry is an awesome debugging tool but it is too easy to leave breakpoints like the following in your code
... some recipe code
require 'pry'
binding.pry
... more code
The text was updated successfully, but these errors were encountered: