Expose history.entries on memory history

[fdecampredon]

While history.entries is not possible on browser or hash history It would be still very useful to expose it on memory history especially for mobile applications where stacks render not only the current route but all the previous one.

[Nantris]

Is this feature dead in [email protected]? That would be a damn shame that locks us on [email protected] forever.

[Nantris]

It seems like it would be trivial to expose. Is there some rationale for no longer exposing entries?

I'm guessing/hoping it's just to standardize the API across router types? It's really limiting for us though and I'm not seeing any alternative to access the history's entries.

@mjackson @pshrmn @timdorr

[FabianMeul]

Also wondering why entries are not exposed on MemoryRouter. Just like @fdecampredon, I want to render the previous route but without access to the entries it leaves only manually tracking the entries... (and duplicating what's already in history)

@mjackson @pshrmn @timdorr

[quiram]

In case it helps with the decision, we currently use history.entries to adjust the text in the back links of our web application. I understand that exposing the entries perhaps wasn't initially thought of as a feature but it looks like it's becoming one that people depend on.

[Nantris]

We're totally dependent on it. We had no idea that we were looking at an impossible upgrade path by using properties which were exposed without any warning that they'd disappear in the future.

[Donorlin]

Any news about this, please?

[Nantris]

Anyone following this should take a look at #939 submitted by @Donorlin. A big thanks to @Donorlin for creating the PR!

[Nantris]

Bump.

[trungutt]

Bump