Fork me on GitHub
#untangled
<
2016-06-03
>
currentoor06:06:50

Thank you guys so much for doing this (and open sourcing it)!

tony.kay17:06:24

I'm changing versions (0.4.11 is going to be 0.5.0 because of breaking changes).

tony.kay17:06:38

I'm in the midst of removing the need for the root re-renders

tony.kay17:06:01

this will be a breaking change, but will restore our APIs to be in line with the intentions of Om (follow-on reads trigger renders)

tony.kay17:06:29

as mentioned earlier...I'm renaming that key from :reads to :refresh

tony.kay17:06:40

it will be available in all forms of load-*

tony.kay17:06:52

including the action (internal to mutation) versions

tony.kay17:06:45

This should also finish removing the easy but slow algorithms from the common paths. The only one that will remain is tempid remapping, which is currently written to be fully recursive on the entire app state. I'm going to add the ability to let users override the algorithm...since optimizing that will require app-specific knowledge

tony.kay17:06:08

FYI: Just pushed 0.5.0-SNAPSHOT to clojars. See the docstring on load-data.

tony.kay17:06:34

should work, but I have not tested it heavily (beyond unit tests)

tony.kay17:06:43

and running one app with it

tony.kay19:06:23

Untangled client 0.5.0 just released to clojars. Note the small breaking change. Cookbook updated on develop. Waiting for a fix to websockets that will fix the websockets recipe (which was relying on root rerendering that has disappeared)

tony.kay20:06:19

websockets 0.2.0 released, and updated cookbook pushed to github