Fix issue #15 where escaped escape chars were treated as escape chars

[derek-miller]

No description provided.

[doowb]

Thanks! I'll take a look at this and get it merged tonight.

[yairk]

Any chance to get this merged, @doowb, @jonschlinkert ? I was bitten by this too, and really need the fix.

[yairk]

Reviewing the pull request again, I suspect that the code counts the number of backslashes before the opening quote, and uses this to decide if the closing quote candidate should be respected.

In other words, given the string '\\\\"hello.world\\"', the code will (correctly) decide that the opening quotes are not escaped, but will wrongly decide that the closing quotes are escaped because it doesn't count the number of backslashes before the closing quote.

@derek-miller - I know it's been a while, but did this code work for you?
@doowb , @jonschlinkert - If you agree, I can submit a corrected PR if there's interest from your side and you're still maintaining this project.

[jonschlinkert]

Hey @derek-miller and @yairk sorry it has been so long. I just noticed the same bug myself, and was about to do a patch, but I'd be happy to accept this one. @yairk if you want to do a patch still I'd probably merge this first so both of you get attribution. It's up to you.

[yairk]

Thanks for following up @jonschlinkert! As I noted above, I believe the current PR is incomplete because it counts the number of backslashes that appear before the opening quote, rather than the closing quote.

I'd be happy to submit a patch - LMK if you want me to submit it based on the currently-released code, or if you'd like to merge this PR first.