History and bw compat. Fulcro 2.0 didn’t have mutations that would self-return themselves as data, so you had to use syntax quoting to put things in them [(f {:x ~a})]` which was kinda ugly. So, since post mutations often needed params my early design choice was to let users avoid the quoting by doing it that way and constructing the EQL for them.

We could add yet another option (`:post-txn` ?) but it’s getting a bit cluttered already 😄

Couldn't we extend post-mutation to accept both, either a symbol or the full mutation = list?

then what do we do if they give a list AND :post-mutation-params? Merge the params? Ignore them? It gets messy

That is true but I would allow them to shoot themselves into the foot by providing params that will be ignored. To me the possibility to use the simpler and more natural :post-mutation (my-mutation {..}) is worth the small risk of some ppl trying to mix the two. But YMMV, of course.

could also do that with a new name for df/load! ?

same problem: larger surface API, and I’m not sure I think it’s worth it for such a simple thing you can accomplish with a wrapper of your own. If we had some idea that added something of significance, then I’d be more inclined. As it stands it’s just pretty trivial.

Hey Greg. This is probably more appropriate in one of the jobs-related channels. I’m ok with it here, unless it spawns a swarm of job hunting 🙂