Closed markjen closed 7 years ago
oh crap. You are right.
will fix.
thanks @markjen
Hi @markjen the goal is to never have a false positive, so this is an error, not a design change.
I just pushed a fix and we release shortly.
Could you verify it's working for you and report back?
thanks for your report.
n
fixed in release 0.2.1
Looks like a recent change has switched this tool to be case insensitive, causing false positives like this:
"importEnd" is a misspelling of "imported"
The README currently says the tool is meant to understand camel cased code and parse it as multiple words; not sure if this is an intended design/behavior change or an issue.