Hacker News Reader

Comment by vbezhenar | Hacker News Reader

IMO React is missing hooks to work with promises. I made that hook myself but I think that promises along with AbortSignals (to interrupt promise if React decided to cancel it) are basic JS API and React should just support them out of the box. I saw too much code which deals with async functions in useEffect in a buggy way. Things like ReactQuery are nice but they should not be required.

Here's my implementation, for the record: https://pastebin.com/rjj0FDDd

View on HN

We agree. https://github.com/reactjs/rfcs/pull/229

You probably won‘t answer, but what do you think of the (imo uncalled for) wishful thinking that react should‘ve stayed in the direction of Class components?

Dan wrote an answer today about classes here: https://news.ycombinator.com/item?id=35188669

Missing standard downstream promise cancellation is arguably one of the bigger problems in the whole javascript ecosystem. In C# almost every async function has a CancellationToken parameter, same in Go with Context.

Even after years of writing fullstack javascript this is my first time seeing AbortSignals, probably because nobody uses them. Some libraries, like Axios, handroll their own cancellation mechanisms, but that does not really cut it.

> Here's my implementation, for the record: https://pastebin.com/rjj0FDDd

This implementation doesn't account for the fact that the promise may settle after the component has been unmounted.

react-query basically converts promises to hooks

Reply on news.ycombinator.com