Handle BUILD_ID mismatch error

[arunoda]

Provide a hook to handle the BuildID Mismatch error.
If the hook is not provided we'll throw an error like below.

It'll ask to visit this wiki page for more information.

[nkzawa]

I think we can navigate pages with normal browser transition as default instead of pushState in this case. This wouldn't trigger Infinite loop.

Additionally, we can provide a way to replace this behavior like onBuildIDMismatch((e) => e.preventDefault()).

[arunoda]

@nkzawa That's something pretty cool.

[arunoda]

Anyway, again it's the same as writing location.reload() in the onBuildIdMismatch() hook.
But actually changing the route. (Which is good)

@rauchg what do you think?

[nkzawa]

@arunoda It looks location.reload() is not the same since onBuildIdMismatch is called before url change on push.

[arunoda]

@nkzawa yep. I mentioned it on the comment.

May be we could pass the next page URL to the hook.
Why we go with this approach is this might reset the client state of the app.
So, it's a user's responsibility.

[nkzawa]

btw onBuildIdMismatch can be onAppUpdateDetected or something ? I think users don't need to know what BuildID is.

[rauchg]

@nkzawa the only issue with that is that it implies new code, while we can't really guarantee that. You could have rolled back to an old version for example

[arunoda]

You could have rolled back to an old version for example

I'm quite not sure about this.
User need to only intervene to persist and restore the client state.