just pushed an update to 0.6.0-SNAPSHOT. Includes a couple of little bug fixes

Are you guys open for a pull request so I can set the shared property of the reconciler?

@adambros Ooops. Yeah, the way return handler is written is wrong. My bad. We're in the middle of a swap at that time, so swapping is going to break.

@mitchelkuijpers We’ve had a lot of success putting shared state in the app db.

@gardnervickers we have some global stuff like a certain base url and in which product we are (we are writing a plugin for multiple products) and now we just reference global values, but setting a shared value on the reconciler is way nicer. Then you can use om/shared in your components to reference them

And it is pretty handy with devcards ^^

@mitchelkuijpers sure, but I think DNolen deprecated that feature in favor of link queries

We had a similar setup, where there was some global state we wanted to read. Putting it under the root of the DB and just querying for it like [:my/thing ‘_] worked well, and I couldn’t figure out a case where shared makes more sense.

though I seem to remember there was some use-case he was considering leaving it for

Oh ok.. maybe not a good idea to add support for it then

it's a trivial add, so feel free

Also I had a question about using the new load to load a simple property from the server like [:foo] I currently still use load-data for this

because of the required SubqueryClass

@gardnervickers We mostly used it because of reasons 😛

:shared is not deprecated, and it serves different use cases than link queries

«now 90 1 / 20 fno tI can’t call me call me.1 hyphen

Then I will create a pull request 🙂 thnx @anmonteiro

@mitchelkuijpers merged and I pushed a SNAPSHOT update to clojars

Oh, and the load API. Hm, I guess in that sense load-data was more direct. How about we make the class optional?