This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-13
Channels
- # aleph (5)
- # beginners (92)
- # cider (37)
- # cljs-dev (38)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (50)
- # clojure-berlin (1)
- # clojure-canada (3)
- # clojure-dusseldorf (4)
- # clojure-france (1)
- # clojure-germany (1)
- # clojure-italy (7)
- # clojure-nl (21)
- # clojure-spec (2)
- # clojure-uk (106)
- # clojurescript (165)
- # code-reviews (1)
- # community-development (3)
- # cursive (5)
- # datomic (13)
- # editors (12)
- # emacs (3)
- # figwheel-main (141)
- # fulcro (28)
- # graphql (1)
- # immutant (1)
- # jobs (1)
- # jobs-discuss (5)
- # midje (8)
- # nrepl (3)
- # off-topic (28)
- # onyx (4)
- # re-frame (21)
- # reagent (70)
- # ring (2)
- # ring-swagger (9)
- # shadow-cljs (18)
- # spacemacs (6)
- # specter (23)
- # tools-deps (21)
@U0D8J9T5K Don't know about success, but I'm doing it
The problem is the same as with ES/JS React app: there doesn't seem to be a really fitting map component. The map wants to handle its own DOM, and it keeps the markers in a kind of a virtual dom
The wrappers I've seen don't really do anything smart. IIRC if anything in their data changes, they will just erase and recreate everything
This might be obvious, but why call the larger app state “coeffects”
@drewverlee I believe the docs mention some details on this concept
ah ok. ill give that a read, its on my list.
Can anyone explain the why re-frame uses the interceptor pattern? I believe i understand the pattern, but i’m not sure i understand why it makes sense to organize things this way. I don’t have strong feelings one way or the other i’m just interested if there are any notes on why 🙂
@drewverlee: http://tomasp.net/coeffects/ is a good read on coeffects (pretty sure it was part of the inspiration)
intresting! Thanks, i wasn’t sure if that was related
@drewverlee Your request confuses me. You say you understand the pattern then express doubt without making any point whatsoever as to why. Do you see a fault in the pattern? Do you like a different pattern? This comes, btw, from someone not enamored with the pattern!
I should have asked if anyone knows if there is a rational anywhere that explains its use with re-frame. I’m guessing the author had his reasons, i’m curious if he jotted them down anywhere. I use “understand” fairly loosely here, I read over several high level explanations of the pattern and a blog post that gives one explanation of how it fits within reframe.
Well, you are right. The author has produced an amazing amount of quality doc but nothing I can recall justifying the architecture. Given things like Redux and Ring, maybe middleware is just the default framework design. Me, I do not like frameworks period.
So I am curious. Got an alternative in mind?
btw, I just got reminded of Mike’s distinction between interceptors and middleware, so forget everything I said. 🙂
Can anyone point to some larger re-frame apps in the wild that are on github? Something even larger than the conduit-reframe for example.
This may be bigger, depending on your metre stick: https://github.com/kennytilton/rehiring That page has a link to the live version (albeit using my JS hack, but otherwise a straight port). I also have an exemplar doing some magic on Ajax callback hell. Throw me a challenge feature-wise, I’ll try to knock it off.