This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-05
Channels
- # architecture (2)
- # aws (1)
- # bangalore-clj (4)
- # beginners (97)
- # boot (35)
- # cider (8)
- # cljsjs (3)
- # cljsrn (35)
- # clojure (190)
- # clojure-dusseldorf (4)
- # clojure-italy (7)
- # clojure-poland (1)
- # clojure-russia (17)
- # clojure-spec (74)
- # clojure-uk (30)
- # clojureremote (2)
- # clojurescript (298)
- # code-reviews (18)
- # component (18)
- # cursive (18)
- # datascript (3)
- # datavis (2)
- # datomic (24)
- # dirac (17)
- # emacs (3)
- # garden (7)
- # hoplon (51)
- # jobs (2)
- # jobs-rus (2)
- # leiningen (4)
- # luminus (11)
- # mount (24)
- # off-topic (1)
- # om (32)
- # onyx (25)
- # pedestal (1)
- # powderkeg (9)
- # protorepl (6)
- # re-frame (11)
- # reagent (15)
- # spacemacs (6)
- # sql (35)
- # uncomplicate (1)
- # unrepl (74)
- # untangled (130)
- # yada (6)
Hey, how to get path/query
string's from goog.history.Event
.
(or how to route a re-frame with path/query params?)
@miikka Nope, FAQ addresses this issue pretty well: https://github.com/Day8/re-frame/wiki/FAQ#1-why-cant-i-access-subscriptions-from-event-handlers
Form state goes in the main app db just like anything else, validations as event handlers or in a subscription, I've created builders for complex forms but it's all very dependent on the specific cases.
@miikka If you have a good understanding of how to separate subscriptions and events, consuming subscription from an event does make sense. It may be added in the future but there is a 'hack' for now if really needed. https://github.com/Day8/re-frame/issues/255
Is it suitable to create view/event/subs/db on a component base? Or do you suggest to use it for routes?