would be nice if df/load-data and df/load-data-action accepted the param :post-mutation-params like df/load and df/load-action. i’d like to load many top level keys in a single request, then consolidate and process the results in a single post-mutation with params. currently working around this problem by calling df/load for each key, then setting post-mutation and post-mutation-params on the final df/load.

@ianchow The networking layer of Untangled composes all loads made on a single thread's sequence into a single network request. I.e. 10 calls of load will make 1 API network call as long as you do it all on one event. Calling load just places something on the network queue. When you let go of the thread, then it processes the queue. The only thing to know is that remote writes are reordered to come before reads (e.g. if you do some transact mutation and some reads all in the same cluster, then the writes will execute on the server before the reads).

That said, it is trivial to add the extra params to those APIs. I'm not happy having both (load-data and load). The original intention was to replace load-data with load (deprecate the old API). I have not had enough time to look to see if that is reasonable, but it's also why I didn't spend time adding new things to the old call.