Fork me on GitHub

there is a way to use :shared variables with Untangled?


Just from conversation earlier about 'Autocomplete' with Untangled. The actual Autocomplete tutorial fetches from Wikipedia when 3 or more characters have been entered. So no need for debounce but more importantly the client is not interacting with an Untangled server, but some Wikipedia URL. So load-data (which is now called load-collection ??) can't be used - I don't think...


@cjmurphy: load-collection is deprecated i think, load-data is new name


@cjmurphy: you can use a custom network handler if you want to something different from the default, it's not well document yet but if you look at the sources you can see their HTTP networking implementation, from that you can figure out how to implement your own


@cjmurphy: You can certainly use whatever additional networking you want, and use om/merge! on the reconciler to push it in. We have not needed multiple remotes yet, but I'm wanting to add is needed. Also, might make sense to add something that assists with things that are more REST-y in general for this kind of use-case. Any ideas are welcome...we don't have the specific use-case yet, but want to fully support what is generally needed. And correct: we did have load-collection and load-singleton (alias) and unified those into the single name load-data


BTW: Talk from last nights Clj West Unsession is up on YouTube (processing, but link is):;


I'll be mixing in the live action video in a few days...right now it is just audio/slides. They don't record the Unsessions, so I had to manage it myself (the downsides of open-sourcing after talk submission deadlines :) ).


@tony.kay: I'm thinking about the :shared issue here, I really need to add shared objects on my UI, I was thinking about what would be the best way to add this option


I think the point to add would be when creating the client, but I think it's a long chain to be adding parameters to all functions in the middle in order to reach the reconciler construction


actually, sorry, looking again it seems like it could be added to the application info, and then used when creating the reconciler


I’ve got a UI that renders a list of items and a form + mutation for creating a new item (and appending it to the end of the list). If I define the mutation callback in the root component and pass it down to the form then it works perfectly. However if I define the mutation lower in the ui-component tree the UI gets all messed up when the mutation is triggered.


@currentoor: If the mutation is adding onto the end of the displayed list then it really is affecting the whole list, and so needs to be done on the component that contains the whole list (thus the function is passed down). Only a mutation that say just say just toggles a check-box could be on the item component.


@cjmurphy: ah that makes sense!


Also I see we have 84 members now… there are dozens of us… dozens!


This one will go up and up for a long time I believe simple_smile


@adambros: :+1: