I have some questions about the request lifecycle in middleware

[wonu]

1. According to the document Sharing Context Between action and loader, the context value set in the action phase can be used in the loader.
   I assumed that the request in the action phase and the request in the revalidation phase were separate, and thus the context would be independent for each. Is that not the case? How is this possible? (My apologies if this question sounds strange, as I'm new to this topic.)

2. I followed the example in the document, but the loader only contains the default value instead of the value set in the action. Did I do something wrong? Repro: https://stackblitz.com/edit/github-165puddz?file=app%2Froutes%2Fhome.tsx

3. Is there any point in setting the context value within the loader/action instead of the middleware?

[sergiodxa]

I think the example is wrong, as you noticed, the POST request the triggers the action and then followed by a separate GET request, each request has its own router context instance making it impossible to share a value between them.

However, this is true if the POST request was also a document request, in which case the same POST triggers the loaders, allowing the sharing of the router context instance.

I think the example needs to be updated to mention that only works for document requests, cc @brookslybrand

[brookslybrand]

Good point, this example doesn't seem right

@brophdawg11 did something change with how middleware works or is this example intending to show something and just needs to be tweaked?

[brophdawg11]

yeah - on the server context is request-scoped so on document requests you can share but on SPA navigation requests you cannot.

On the client (clientMiddleware, clientLoader, clientAction), because there no HTTP request - you can always share context

I'll push up an update 👍