A luxuriously simple and powerful way to make front-ends with DataScript and Reagent in Clojure.
posh looks pretty awesome :)
was doing a kind of full rerender approach before, but I think reactive q and pulls will be a lot cleaner/faster
hi @alexisvincent thanks! I don't remember exactly, but basically I had to come up with a bunch of rules for various scenarios in
q. A simple case would be where q is looking for [?e :some/attrib ?v], then you just look for anytime any transaction with :some/attrib occurs. The functions for figuring this out are insrc/posh/lib/q_analyze.cljc. The simpler version is called pattern-from-eav--old, which is more easy to understand but generates patterns that are much less specific than the query. ("eav" is an entity-attrib-value rule). The more complex function is called pattern-from-eav and unfortunately it worked really well until we found out it missed one common case, which I couldn't figure out how to fix, so posh is just using the simpler one for now.
@alexisvincent Oh yes you could use that initial set of datoms to sync with datomic. if you call
q-analyze with the :datoms flag you'll get a list of all the relevant datoms for a query, which you could run on the datomic db and then just send all the datoms over to datascript. How the :datoms thing works, if I remember correctly, is the original query is changed so that instead of returning the stuff specified in the :find of the q query, it just returns all possible combinations of the ? query vars in the :where eav rules. Then to construct the datoms, it goes through all query eav rules and replaces all the ? vars with every possible combos.
to get the actual query results with the :find constraints, it just runs
q on the set of possible vars (not the whole db), so it should still be pretty fast
The catch set might be too large though
Have you looked at the Datsync project? They've been working on syncing between datomic and datascript for a while now. I don't know how it's going, but they are active at least.
@orolle Posh should be faster because it doesn't make full queries or pulls every time there is a new transaction, only when a new tx will change the result of a pull/query (this is assuming we're comparing it to a rum + raw datascript that redoes all its pulls/queries every tx). In posh,
pull is more efficient than q, so you might be able to get away with a large ui if you use mostly pulls.
i'd just recommend doing some testing before you commit to using it
hey @mpdairy first of all thanks for the great work that you have done with posh !! that is definitely the missing piece in reactive programming that I was looking for.
I just started working with it and got some errors using pull. I checked the source code and Cursive showed me that there are three functions used with less than their declared arguments; namely
posh.plugin-base/missing-pull-resultline 20 and 22posh.plugin-base/get-dbline 127
The error that I get is this
object[TypeError TypeError: null is not an object (evaluating 'new cljs.core.Keyword(null,"conn?","conn?",167224275).cljs$core$IFn$_invoke$arity$1(dcfg).call')]
posh$plugin_base$get_db
cljs$core$IFn$_invoke$arity$5
posh$plugin_base$pull
cljs$core$IFn$_invoke$arity$4
G__10589__3
G__10589
eval code
eval@[native code]
figwheel$client$utils$eval_helperSince I just started working with posh, I am not sure if this is a problem with my configuration or an actual bug in the implementation, so I wanted to ask you first. I am happy to submit a PR to fix that if you want.
@theronic I don't think anyone has done this yet, but there was a bunch of refactoring that extracted most of the stateful bits of things so that someone could add a rum plugin fairly easily. If you're interested in hacking on that, I'd be happy to point you in the right direction there.
@mpdairy I have an auto deploy config with
travis ci for one of my projects. I didnt setup the auto deploy myself but I think that the file is pretty self-explanatory. The only things that you would need to change are the your encripted env vars and your release config in project.clj. Links below
This message was deleted
Hi, I'm trying to get re-posh working with my app, but my pretty simple req-query-sub seems to be causing an "Assert failed: (db?db)" exception. Not sure what's going on. I was pulling in the datascript conn via mount, removed that, still have the problem, and did some mucking around and determined that calling connect! without a valid conn, throws an assertion there. So it seems like as of connect! things are fine. unfortunately the stack trace isn't really helping me figure out whats going on. I tried the query with and without ':in $' to no avail
figured it out, but not sure what the problem is. When I got rid of the pull, everything was ok. But I'm not sure why pull isn't happy. been over the DS, etc docs and it seems like it should
(reg-query-sub
:cur-form-def
'[:find (pull ?e [*])
:in $
:where
[_ :designer/cur-form-id ?id]
[?e :form/id ?id]
])
There are two problems in Reagent land I keep running into: I forget to update Form-2 component arguments, and I can't get posh to re-render things when I expect to. I want to display the entire the posh db at the bottom of my page so see what's going on. I can never remember when I should deref conn or not. Why doesn't
[:code (pr-str @conn)] inside my root component re-render on every db change?
But wait a little bit. Maybe somebody else has a better idea
https://github.com/bamarco/onyx-sim/blob/master/src/cljs/onyx/sim/core.cljs using make-reaction like i do in
debug-conn here will work. Haven’t really stress tested it though might just be getting lucky. If you want to be more efficient you could rig up a listen! on the conn.
@orolle Not at present. I did some preliminary work trying to get it working, but couldn't quite sort it out. In theory it should be possible, as long as you're not putting functions or anything weird in your db. We are looking at the possibility of putting this in datsync fwiw.
Is the remaining issue that it won't garbage collect properly/automatically?
I fixed a small bug that was hiding the big one from me.
It may only be a problem with nil starting values. haven't tested yet because all my code in onyx-sim is re-com based and not rum compatible