Yeah, I was sort of resistant to it for some time because you can use returning to get a normalized merge of the return value, so it seemed like “encouraging misuse”…but there does seem to be a class of useful cases where you don’t really need the return value in app state, but just sort of need it in some kind of transient fashion.

so I got tired of having to manually decode it out of the raw network result 😄