The person that asked the question isn't using redux correctly
redux's state becomes very useful in that scenario because now, both blog posts exists in app state, and the user will only see the most recent one he clicked (the one he is interested in) - despite it taking longer to fetch than the first one he clicked
It's a bit confusing for users because they know which order they asked... especially if app uses a commong area? (my question is not innocent since PAL enables a generic mechanism to solve that problem with SAFE)
I meant, you are on a view where you see a blog lists and you ask for some details, you can see the post details or the author's details. You click on post, then you change your mind, you click on author, wouldn't you expect to always see the results of your last request?
Yes, this was my original intent, this is a consequence of V = f(M). All API calls are within Actions/Proposers or the Model/Acceptor.
the view never gets to call an API it publishes events/intents and it get generated reactively, there is not "inter-action" (request/response). That's the major step forward coming from reactive unidirectional data flows.
(I'm tring to map my mental model of redux to PAL) In redux the actions are only intents too. They are pure JS functions that return a description of an action. later on, when the user initiates an action (intent) the dispatcher then executes it