This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-09
Channels
- # beginners (22)
- # boot (80)
- # cider (6)
- # cljs-dev (5)
- # clojure (190)
- # clojure-berlin (5)
- # clojure-dev (24)
- # clojure-italy (14)
- # clojure-russia (70)
- # clojure-spec (39)
- # clojure-uk (82)
- # clojurescript (121)
- # clojurewest (1)
- # core-logic (2)
- # cursive (25)
- # datascript (186)
- # datomic (33)
- # dirac (266)
- # emacs (9)
- # gsoc (4)
- # hoplon (37)
- # immutant (34)
- # instaparse (22)
- # jobs (4)
- # juxt (6)
- # lambdaisland (2)
- # leiningen (1)
- # liberator (1)
- # luminus (5)
- # lumo (28)
- # off-topic (9)
- # om (23)
- # onyx (26)
- # other-lisps (1)
- # parinfer (39)
- # pedestal (45)
- # proton (1)
- # protorepl (10)
- # re-frame (18)
- # reagent (4)
- # ring-swagger (8)
- # rum (4)
- # specter (13)
- # test-check (14)
- # testing (1)
- # unrepl (164)
- # untangled (10)
- # yada (14)
Is ist possible to create a cursor to a component, which I could save in the re-frame db, instead of the whole component?
@danielgrosse what do you mean by "cursor to a component"?
having been away from 0.6.0 to 0.9.2, what happened to the need to use reagent.atom/reaction
inside subscription handlers? or is that still a thing? (i don't see it in the README anymore)
@pandeiro: Lots has changed since then - read through https://github.com/Day8/re-frame/blob/master/CHANGES.md first, probably worth reading through the new README and docs as well. Huge improvements and it's a lot nicer to use now.
thanks @shaun-mahood I've been doing that in bits and pieces; this was just one major change that I didn't see specifically explained anywhere
@pandeiro: Specifically, the subscription was changed in 0.8.0 - 2nd bullet point under https://github.com/Day8/re-frame/blob/master/CHANGES.md#080--20160819---the-walnuts-release
@pandeiro: If you're interested in watching video on it, I think you might find something useful in my talk from the last conj - although it was meant for everyone, my own context came from learning 0.6 -> 0.9 and so most of it should be pretty relevant for your own path (though I haven't been able to bring myself to actually watch it yet, so I can't guarantee the quality... 🙂 )
thanks that sounds like a good investment -- the link to the develop branch's docs (in that same 0.8.0 changelog item) is a little bit 😮 just b/c of how much stuff there is there
Yeah there's a lot there - the changes have been pretty amazing as far as how much they've improved the few main issues I ran into with 0.6, but the fundamentals are still very much the same. It was a pretty impressive amount of work that Mike and Daniel put in.
Hey all. I"m trying to figure out how to pass query-params to my panels I have the router setup as such
(defroute "/job/:job" [job]
(re-frame/dispatch [:set-active-panel :job-panel]))
The only way I can think to past job-id to my db atom and access it from there, but that has obvious race conditions. I feel like I'm missing something obvious@danielcompton @mikethompson @shaun-mahood Have you thought about adding an option to use Datascript as the app-db
? How difficult would it be to implement?
There is https://github.com/Day8/re-frame/issues/151. We've thought about it, but have no particular need for it ourselves. It would be fairly easy to swap out app-db for datascript, you would just make a new reg-event-ds
function which injects your datascript db and applies modifications after the event. It doesn't even need to be part of re-frame core, as all of the raw primitives are there for you.
is this what posh does? https://gitter.im/mpdairy/posh