This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-05
Channels
- # beginners (23)
- # boot (84)
- # braid-chat (2)
- # bristol-clojurians (1)
- # cider (53)
- # cljs-dev (34)
- # cljsrn (13)
- # clojure (138)
- # clojure-dusseldorf (5)
- # clojure-italy (1)
- # clojure-russia (164)
- # clojure-uk (41)
- # clojurescript (80)
- # clr (2)
- # core-async (6)
- # core-logic (25)
- # core-matrix (14)
- # cursive (10)
- # data-science (4)
- # datomic (4)
- # emacs (3)
- # funcool (6)
- # hoplon (127)
- # jobs-discuss (4)
- # keechma (36)
- # ldnclj (5)
- # lein-figwheel (5)
- # off-topic (5)
- # om (155)
- # onyx (72)
- # overtone (16)
- # parinfer (39)
- # planck (3)
- # protorepl (1)
- # re-frame (11)
- # reagent (5)
- # untangled (22)
@roberto you could, but it would go to the wrong "instance" of the controller. Params function is called before the controller is started. Why not calling it from the start
function?
I have a component that is already rendered, and want to modify it everytime the url changes.
you get the route-changed command sent through the in-chan everytime route changes
it basically clears the stale data from the entity db on each route change
controllers operate on the route
they don't really care about components
okay, I think it is kind of clicking. So, the only way a component can be linked to a controller is via its topic
. And it can only be associated to one topic, hence only to one controller.
but that doesn’t restrict it from sending commands to other controllers using the send-command
, right?
it does because the component's send command will always send it on it's one topic
but if you need to broadcast the message
theoretically you could add a transducer
on teh command channel
and duplicate commands
to various topics
also, controllers can send commands to other controllers
so you could have a controller that relays commands from the component to other controllers