Add back functionality to navigate route

[stasiukanya]

Implements #44

Uses history.go as suggested by @ryanflorence in #44 (comment)

[enzoferey]

Any chances this gets merged ? I think this is pretty useful for Gatsby as the window object can't be used during build process.

Related to this issue.

[brion-fuller]

Any update for this PR?

[peterlaxalt]

Would love to see this get merged. 🤘

[icyJoseph]

Does this implementation re-render the previous tree? #44 (comment)

[erasmuswill]

This would be great!

[bpurtz]

+1

[calpa]

Why not merge this commit?

[revskill10]

+1000000

[crutchcorn]

Please refrain from adding +1 comments. Adding emoji reacts communicates the same enthusiasm for the work without cluttering the thread

[tanigaki39]

+1

[erasmuswill]

+100

[blake-hunsicker]

+1000

[lesmo]

I believe that the createMemorySource should also implement this expected behavior on the history::go method. It's currently undefined.

[erasmuswill]

+10000

[Kadrian]

Coming from Gatsby as well, wondering why it's still not possible to simply .goBack().

So, what's missing for this PR to get merged?

Feedback from @ryanflorence ? Clicking "merge" by @stasiukanya?

[ryanflorence]

Thanks for your patience.

My hesitation here has been around how suspense and caches are going to work.

If you click "back" do we need to go into the transitioning state or can we assume since we're going somewhere we've already visited the cache will be filled already?

This PR assumes the cache will be filled. And I suppose the code already assumes they will be filled if the user clicks back.

Anyway, we may find issues when suspense ships in 2032, and we can figure out what to do then.

(j/k react team I love you suspense is going to be amazing)

[LouiseReid]

Should this now be working as its merged to master? I'm using v1.2.1 and passing an int to navigate just attaches it to the end of the url

[ZeeEssDoubleU]

I'm having the same issue.

navigate(-1) just appends '-1' to the end of the url

[erasmuswill]

When this works I have some production workarounds to rectify xD

[ricksmit3000]

this doesn't quite work yet with in the beta release: to === "/-1" so it doesn't pass the typeof to === "number" check. somewhere it prepends to with a slash.
sorry issue was actually in gatsby-link

[mckelveygreg]

I'm also on 1.2.1 and it is just appending a -1.

[ricksmit3000]

Yeah so the fix is on the beta release, so just do ‘yarn add @reach/router@next’

[luistak]

In some use cases I suggest:

<Link to="../">Back</Link>

[adamthrottleup]

I am also seeing the issue where navigate(-1) is appending a -1 to the url.

I ran ‘yarn add @reach/router@next’ as suggested by @rickiesmooth but the issues persists. Any fix for this yet?

This is my implementation in Gatsby

import { navigate } from "@reach/router";

const goBack = () => {
navigate(-1);
}

<a onClick={goBack} className="back-link">Back</a>

[adamthrottleup]

I am also seeing the issue where navigate(-1) is appending a -1 to the url.

I ran ‘yarn add @reach/router@next’ as suggested by @rickiesmooth but the issues persists. Any fix for this yet?

This is my implementation in Gatsby

import { navigate } from "@reach/router";

const goBack = () => {
navigate(-1);
}

<a onClick={goBack} className="back-link">Back</a>

FYI I fixed this by updating my project's packages to the latest versions by running
yarn upgrade

I'm assuming this worked because I got the latest fix to gatsby mentioned above (gatsby was updated to v2.24.63)