Do not remove trailing slashes, when dealing with relative urls.

[badazz91]

see #70

[alexlafroscia]

@badazz91 can you add me as a collaborator on your fork? I added a failing test that is introduced by your changes.

It is implemented the way it is right now, always ensuring a / at the beginning and no / at the end, is so that the method can be used to sanitize any of the URL segments that might be passed in from the namespace or host option on the service or from the request options hash. By not removing the / at the end, we break the fact that sometimes that behavior is depended on, so the change to fix #70 will have to leave this method the way it was originally.

[badazz91]

@alexlafroscia I added you as a collaborator.

[alexlafroscia]

@badazz91 great, thanks. I added the commit with the failing test.

[badazz91]

@alexlafroscia We made some modifications, to satisfy the failing test. Let me know about your thoughts.

[alexlafroscia]

I added some more test cases, found a place where they fail again. I still feel pretty strongly that _normalizePath should be left as it was, to ensure that all the segments end up in the same format (/ at the start, no / at the end). Maybe checking if the full URL has a trailing slash, and then add it back at the end if it needs it?

[alexlafroscia]

Closed in favor of #96 which was merged a while back.