Clojurians Log v2

can’t see a good reason for that, it could be it was written before post-mutation-params were it should be easy enough to add it, or just pass-through all the params here: https://github.com/untangled-web/untangled-client/blob/develop/src/untangled/client/data_fetch.cljc#L234

@therabidbanana Oh right, it is already a map by then. Yeah, this is an Om Next limitation.

@wilkerlucio Post mutations: the full env isn't really available at that stage. You're not in parsing anymore. The post mutations are not first-class, in that we're not running transact, we're processing a response. Chaining (e.g. the server says something in response to a mutation, and that makes you want something else) make me nervous. I have not wanted to encourage that, and would want to talk about the use-case before considering it more.

@wildermuthn Untangled gives a specific decisions on a few things in the overall approach to Om Next. The choice of using REST-based server stuff is possible (and done essentially the same way): You probably plug into the client-side network layer and do the translation there.

hello guys, little question, is there a css-lib on which untangled-ui is based ?

It is inside of untangled-ui itself

@stephenway can speak more to it

@wilkerlucio Pushed 0.8.1-SNAPSHOT to clojars. It has your post-mutation-params addition PR

anyone else looking for post mutation params on data fetch methods: it should be complete now on that

@w1ng ^^^

@tony.kay thanks 🙂

Thank you

👍😀