This doesn't look like the right fix. I'm submitting a pull request against your fork that should take care of this though. Good catch!