Replace backslashes in relativePath by slashes for windows compatiblity

[mecab]

Hi,

I found that options.spritePath contains backslashes when we use the module on Windows. This PR will solve the issue.

[selaux]

Thanks for the PR (and the included bug report :+1: ). To not be required to sniff the platform, we could rather use relativePath = relativePath.replace(path.sep, '/');.

What about escaped backslashes in the path, is that possible?

And for pull requests to be merged here they need to include tests :wink:.

[mecab]

Thanks for the response. Using path.sep is nice👍. I've updated it to use path.sep.

I'm stuck in writing test since we have to change path module's behavior to test the code. Should I have to write fake path module which use backslash as separator, regardless of actual platform?

Please let me know if you have any idea 💫.

[mecab]

Thank you very much for the advise. I think I have done the work.

While proxyquire is nice, I found the more specific code to test getRelativeSpriteDir() so I added proxyquired test for there.

I also added path module's mock for Node.js <= v0.10, which does not have path.win32. It might be poor a bit, but it does its job at least 👍

[selaux]

Damn node 0.10, making things so compicated :wink:.

[mecab]

Sorry for the late response, but shouldn't they be Windows paths then? 'test\img\sprite.png'

Oops, I forgot to include them. Now it's confirmed to work well in the latest commit, with adding more mocked functions😎.

[selaux]

Just asking: What is the status of this? Is this good to merge? To me it looks fine.

[mecab]

Yes, It's ready to merge, I think.