Add support for navigation via browserHistory.

[STEVEOO6]

Users can supply a history object to the Admin component, in order to support using React Router's browserHistory (to make things slightly prettier).

In this case, user's can also supply a basePath string value to the Admin object to use as a entry point to the admin-on-rest UI.

For example, my website is located at http://testwebsite.com. I've set the basePath value to 'admin', so that now I can access the primary client-facing site at http://testwebsite.com and perform administration activities at http://testwebsite.com/admin.

[fzaninotto]

please leave versioning to the core team

[fzaninotto]

I think supporting a custom basePath is required, but supporting a custom history object isn't. The reason why we published the Custom App doc is because I think that as soon as you need to do something fancy, the <Admin> component will get in your way and you shouldn't use it.

I don't want the <Admin> component to become an over-configurable beast that reinvents redux and react-router. If you know what you're doing, don't use the <Admin> component.

So please keep only the basePath stuff here.

[djhi]

You can have a custom base path already. See marmelab/javascript-boilerplate#110

[fzaninotto]

@djhi right, but only with hashHistory

[djhi]

Why ? Isn't react-router hiding the history implementation from us ?

[fzaninotto]

closing as no news for too long