Hi all! For the past several months, I’ve been working on an app with my own bindings for apollo-client and react-apollo that differ from the more official ones in the way they treat GraphQL typings (which is a topic for another post…). I’d like to move mine into a separate repo and OSS them in case anyone else wants to give them a try, but I’m hung up on the best way to handle Promises.
Pretty early on in writing mine, I decided to utilize repromise to to represent the result of any async actions. To me, writing code with repromise feels like a massive improvement over
Js.Promise, and is more type-safe as well. While I’d love to keep using repromise in my OSS bindings, I’m not naive enough to think that some folks wouldn’t appreciate being forced into using that lib ;).
It’s been a while since I’ve looked into what the Reason community is doing in the async space. I know a number of folks have been unhappy with the
Js.Promise paradigm, so I was wondering if anyone knows if a better approach to handling async that doesn’t depend on a 3rd-party library (or, maybe depends on a more accepted-by-the-community 3d party library)?
I suppose the other option would be to write my bindings with
Js.Promise and then also provide an adapter for use with repromise?
Anyway, I’d love to hear people’s thoughts on this! Thanks!