René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Race in the async action example?","articleBody":"I'm wondering about this example in the README:\r\n\r\n```\r\n  // Async actions can be pure async/promise functions:\r\n  async getStuff(state) {\r\n    let res = await fetch('/foo.json')\r\n    return { stuff: await res.json() }\r\n  },\r\n```\r\n\r\nI don't fully understand how you can really support async actions like in this example.\r\n\r\nIf `getStuff()` is called twice before the first call resolves, and the two `fetch()` operations happen to finish in reverse order (because HTTP servers are unpredictable) doesn't this cause a race condition?\r\n\r\nWon't you end up with the `stuff` from the first request instead of the second?\r\n\r\nI understand (from reading [this issue](https://github.com/developit/unistore/issues/3)) that the internal call to `setState()` is defferred until the promise resolves - but I don't think that's enough to guarantee that `setState()` calls are performed in the same order the actions were invoked?\r\n\r\nFor something like an auto-complete input fetching results from the server-side, it seems like there's a good chance of this actually happening.\r\n\r\nDo I have to manually prevent races?\r\n","author":{"url":"https://github.com/mindplay-dk","@type":"Person","name":"mindplay-dk"},"datePublished":"2019-08-02T09:20:16.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/165/unistore/issues/165"}