I associate then with the idea of asynchronis handling. So in the example below the first where i pass a fn to turn a response into json response makes sense.

fetch('')
  .then(response => response.json())
  .then(data => console.log(data));

i guess i is separated in time from the first thing. and given you need a catch it also flattens the logic out.

repeating a commonly known prefix is less noisy compared to nesting various kinds of forms to some? yeah it looks silly to me too

it's almost like an unrolled monad - simplifying the thing by putting every step in the same container

(simplified for human readers taht is)

Right i guess the main concern is avoiding nesting. i guess my first step function could do everything. But i ended up copying the pattern i saw and only later questioned it.

right, but the criteria for nesting here isn't a technical constraint, it's a human reader concern

predictable patterns are a great way to make bugs visible 99.5% of the time and impossible to see 0.5% of the time

especially because using redundancy for clarity increases the chances of accidentally correct reading of what the code does (that leads to a totally incorrect refactor)

@drewverlee it’s because fetch resolves the promise as soon as headers come in, which means that the response might not be fully complete yet

so in this case response.json() returns a promise that resolves once the body is fully available

i see. This makes sense with what i'm seeing. i tried to make it one step and it failed.

this is probably clear in the docs and im reading past it, thank you.

yeah, the API is clearer when you want to do something other than consume json. like stream a binary blob

i guess i picked it because it was "modern" and included. Maybe there is something more tailored for clojurescript http requests?

I think fetch is quite good when used in conjunction with CLJS

no matter what, you’re going to have to deal with async-ness of the request. raw AJAX requires using callbacks. fetch gives you a promise interface, which for a lot of use cases is easier IMO

there’s cljs-http which gives you a core.async interface if you’re already use core.async

Not trying to promote Facebook or anything here -- just already have the pics and a Wikipedia link posted on my page here of a cool thing I noticed in my freezer today: https://www.facebook.com/andy.fingerhut/posts/3239965412693392