nhmood / watson-ruby

inline issue manager
MIT License
634 stars 50 forks source link

Debug/verbose output and read custom file extensions #230

Closed stijnvdb88 closed 10 years ago

stijnvdb88 commented 10 years ago

Hi,

I just started trying out watson and so far it looks pretty awesome!
I gave it a trial by fire by letting it loose on a pretty big project I'm working on, and ran into a few kinks. First, it gave parse errors like this one: /Users/Stijn/.rvm/rubies/ruby-2.0.0-p353/lib/ruby/gems/2.0.0/gems/watson-ruby-1.5.1/lib/watson/parser.rb:222:in 'encode': "\xC2" from ASCII-8BIT to UTF-8 (Encoding::UndefinedConversionError) These errors were caused by watson trying to read files it shouldn't - which was easily solved by --ignore'ing them. To make it easier for users to figure out which files are giving issues, it might be a good idea to add a --debug flag to the terminal command so we don't have to edit parser.rb ourselves to enable output.
Next, I had a few files with funky extensions that weren't recognized by the parser, which I needed to add into the parser.rb _ext array. Although your list is pretty complete, it might be a good idea to allow users to add their own somewhere - in .watsonrc for example?
These are more suggestions than they are issues though, thanks a lot for this beautiful gem!