| >Or when the network is unpredictable, you retry because it's taking too long, then the second request succeeds, then somehow the first request succeeds. This has an atomically low chance of ever happening, and never happening on single threaded monolithic servers. >That's no longer 5 LOC. Okay cool, 7-8 LOC, better than abstracting it into a whole new custom hook. >Congratulations. Do you also do that for authenticated requests? If so, either you are using some kind of hardcoded global variable, or you are not using 5 lines of code. You need to be more specific about authenticated requests, because cookies that are sent back as a response will have directions on how they should be sent back to the server on each request that requires no javascript at all. If you're using token auth with localStorage, which probably isn't a wise idea because you're now susceptible to XSS attacks, then you should already be abstracting that away. >What I'm saying is that for things that are more advanced than basic data fetching, you may want to bring better tools than just fetch + 4 extra LOC. here's a pastebin of my wrapper around requests https://pastebin.com/V33F1f2F it is already highly configured and abstracted. All i want to do in the useEffect is await api.getGamesByDate(), and this should be fine. What you're suggesting is that you support the React team's decision in that I have to have an additional wrapper around my apiCalls just to avoid two fetch calls in Strict Mode. Does that sound logical to you? |
Once you have setup that library (or hook) yes, using it it's indeed 4 lines of code. That also happens for libraries constructed by others.