Remove baseURI from History getUrl result

[Arturszott]

If baseURI is set, history handling can't match the current Route to the one set in routes config. As a result, browser's url is shortened from:

http://www.example.com/base/location/route

to

http://www.example.com/route

This PR includes removal of the baseUrl part while getting the url from history module.

[lingyan]

Thanks @Arturszott I will look into this today.

[yahoocla]

CLA is valid!

[lingyan]

@Arturszott

Supporting baseURI could be tricky for isomorphic apps. For example, removing base path from getUrl() works for client side, but might break for server side if the server side routing is set up differently with the full path.

After careful consideration, we decided not to support baseURI in fluxible-router to keep the logic simpler. Since handleHistory allows you to configure your own history implementation (https://github.com/yahoo/fluxible-router/blob/master/docs/api/handleHistory.md#options), you can extend our History implementation for your app, and override the getUrl() to fit your need.

Thanks for your contribution!

[lo1tuma]

According to the documentation of handleHistory it is only used on the client, as there is no history-API on the server.

The handleHistory higher-order component handles the browser history state management.

So your argumentation against considering baseURI sounds very strange to me.