v6.4 Add the navigation state in the LoaderFunctionArgs

[mattiaz9]

I'd like to know the state passed in the <Link /> component inside the loader function args.

Is it possibile to have this?

[brophdawg11]

Can you explain your use-case a bit more? Gernerally this doesn't seem like a good idea to me since your loader would no longer be idempotent. And since loaders handle GET requests, they should be idempotent by default.

Would a query string be an option? Or would you be better off performing a POST navigation and sending information in FormData?

[brophdawg11]

Ah thank you @devpeerapong for reminding me of the new useRouteLoaderData hook too! That's another good option

[mattiaz9]

@brophdawg11 sometimes you can't have trimmed data because you don't have control over the server apis.
The useRouteLoaderData seems interesting, but it can't always work.
Let's take for instance YouTube. You click on a video and you go to the watch page. In that case you can't pass the state from one page to another, right?

[brophdawg11]

So no control over the server and no parent/child hierarchy to leverage shared data - this is getting to be a bit of an edge case ;)

It sounds like you're effectively looking for a client-side cache accessible via the loader - any reason you can't just set up your own client-local cache? Your loaders can then short circuit and avoid a network call if you find the item in the cache.

Take a look at this example: https://codesandbox.io/s/client-side-loader-cache-tb7ut7

[mattiaz9]

Thank you @brophdawg11. That's probably the best way to implement that scenario!

[brophdawg11]

You're welcome - glad it helped!