hey, i'm working on my first cljs rn project right now and i'm trying to figure out a decent way to make API calls to our server. i've got an ugly partial-solution using js/fetch, but it looks like (as my friend says) "Javascript with parens", and i'm getting into trouble when having to make multiple API calls to fill one resource. anybody got any good direction for me to look?

Hi! I'm the friend! The concern I was voicing was that resetting state atoms inside of nested .then calls (on a js/fetch promise) set off my "there must be a better way" sense (either a way to bring the process closer to clojure semantics or a way to bubble updating app state up to a higher call site). I could be totally wrong—cljs is not a particular area of my expertise.

i believe there is something out there that makes promises and core.async channels play nicely w/ each other

also there is 'promesa'

Which part do u think u want: something that runs in cljs and does network requests nicely, or something that wraps promises nicely and u continue using fetch?

if u think u have many js promisy apis u wanna use directly the latter may make more sense, if this is basically the only one the former could

@carocad yeah i understand it pretty well

it shims goog.require because the normal impl needs a browser context to load js

then it also shims goog.net.jsloader for the same

the component thing is to allow cljs to jack in a root component async'ly after it runs

all of this is for the figwheel loaded case

in the case of making a huge js compiled single bundle of ur app (like for 'prod') this is all irrelevant

The boot-expo thing i released recently basically does figwheel-bridge in way fewer lines in main.js https://github.com/nikki93/boot-expo/blob/master/main.js

figwheel-bridge does some weird wait loop stuff to eval the received js in the right order; my version just does a "right fold" through time of promises ;)

@nikki thanks! so i'm not dedicated to using js/fetch or anything, i just figured it'd be the best way to try to get it to work, as it seems like it's being encouraged as the way to go for http requests in javascript ("future-proof" i think i read somewhere). that being said, i'm doubting i'm going to be using any additional promises other than http requests. so i'm not sure which approach would be best.

oh, and i'm developing primarily for Android (at first) and i had read here: https://github.com/JulianBirch/cljs-ajax/issues/141 that calling XmlHttpRequest was giving people headaches, so that's why i was leaning more towards fetch. but again, no loyalty, just trying to make things easy on myself

@domkm may be able to offer u advice on this tbh

he has used promesa

pardon the lack of specificity, but using re-natal what could be causing figwheel repl not to connect, and saving files not to hot-reload the application?

it does open on my device after running react-native run-android

but it doesn't update when I change the code

I now enabled hot reloading and live reloading

https://facebook.github.io/react-native/docs/debugging.html#accessing-the-in-app-developer-menu

But the figwheel has still not connected

disable both of those

and try lein figwheel at cmdline and manually reload app on phone once

but also make sure it's got the right way to connect to ur computer as a server, be that a LAN ip/hostname or ngrok tunnel or whatever