Expose LocationContext

[onnovisser]

Exposes LocationContext, so it may be used with static contextType (and useContext when it lands). May need an explanation in the docs as <Location> automatically wraps itself in a <LocationProvider> when needed, which this won't do.

[marcneander]

@ryanflorence This would make my life easier now when hooks are out.

[peter-mouland]

I suspect, if you're going to make this part of the public API, then a test will be needed to guarantee it's existence without accidental breakages. Without any tests, you will probably have little luck in getting this merged.

[ryanflorence]

https://reacttraining.com/blog/reach-react-router-future/

Not going to expose context, but useLocation is coming shortly.

Thanks!

[waynevanson]

If the new API interests you however, the migration should be pretty straightforward. The next React Router API, on the surface, looks more like @reach/router than React Router. Most of the changes have a one-to-one mapping between both APIs and some are identical.

It looks like react-router what we should be using, which at the time of writing is version 5 according to the roadmap is 5.1.