[Bug]: useNavigate, <Link> and <Navigate> 'to' types about react-router

[brophdawg11]

If you want to go back - useNavigate is the proper API which accepts a number:

interface NavigateFunction {
  (to: To, options?: NavigateOptions): void;
  (delta: number): void;
}

It doesn't work if you explicitly cast it to string | number since that union doesn't fit either of the overloads, but you can use To objects, strings, or numbers individually without issue:

It doesn't really make sense for <Navigate> to accept a number IMO because going back should only be in response to a user-action - whereas Navigate is intended for redirects. It wouldn't make sense to land somewhere jut to be routed backwards without taking any user action.

<Link> does not accept a number because when going back in the history stack there is no way to determine what URL you are going back to, so we cannot render a <a href>.

[PauloBarrantes]

@brophdawg11 Why is not possible to have the option to go back on the Link Component, something like this: <Link to={-1}

[brophdawg11]

<Link> does not accept a number because when going back in the history stack there is no way to determine what URL you are going back to, so we cannot render a <a href>.