Fork me on GitHub
#untangled
<
2017-03-20
>
tony.kay15:03:34

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

tony.kay15:03:07

@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.

tony.kay15:03:31

@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.

baptiste-from-paris18:03:33

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

tony.kay18:03:04

It is inside of untangled-ui itself

tony.kay18:03:43

@stephenway can speak more to it

tony.kay18:03:30

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

tony.kay18:03:53

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

w1ng18:03:15

👍😀