This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-19
Channels
- # aws (4)
- # aws-lambda (2)
- # beginners (67)
- # boot (38)
- # cider (32)
- # cljs-dev (12)
- # cljsrn (2)
- # clojars (2)
- # clojure (190)
- # clojure-chicago (1)
- # clojure-dusseldorf (2)
- # clojure-germany (1)
- # clojure-greece (3)
- # clojure-italy (5)
- # clojure-russia (6)
- # clojure-spec (47)
- # clojure-uk (10)
- # clojurescript (59)
- # cursive (9)
- # data-science (14)
- # datomic (24)
- # devops (16)
- # emacs (8)
- # fulcro (25)
- # graphql (30)
- # hoplon (123)
- # juxt (15)
- # lambdaisland (2)
- # leiningen (4)
- # luminus (6)
- # lumo (9)
- # off-topic (11)
- # om (7)
- # onyx (8)
- # re-frame (14)
- # reagent (5)
- # ring-swagger (5)
- # shadow-cljs (46)
- # spacemacs (41)
- # specter (8)
- # testing (8)
- # unrepl (31)
- # yada (18)
Does anyone have a guess on re-frame: no :event handler registered for: undefined
error?
It happens when I do a :simple build and seems it is preventing my app from booting up.
maybe you didn't require
the events namespace? @iku000888
I’m using re-com and generating input boxes using a map over a collection of labels. But I get a react warning saying Every element in a seq should have a unique :key
- I understand why the key is expected. I just don’t know how do I add it using re-com, hiccup etc. Anyone know?
not entirely sure about re-com
, but with regular hiccup you can apply key
either as metadata on the object or as key
in the properties-map of the element
Hi all, i'm trying to get my head around an issue, it's idiomatic to dispatch an event on a component's :component-will-unmount
hook, to catch and save user's work in progress ?
@iperdomo personally I don't think it's a good idea. It ties a side-effecting action to a rendering event. You may not have perfect control over when the comp gets unmounted
a better approach would be to save as a an effect of the user-action, i.e. navigating away
or even better perhaps, to save whenever the user provides new input, rather than magically save when the user dismisses the view
@pesterhazy thanks, i was actually reading https://github.com/Day8/re-frame/blob/v0.10.2/docs/FAQs/PollADatabaseEvery60.md
> The broader React community sometimes likes to collocate queries with view components and initiate those queries (via a GET?) within the View's componentDidMount. And then, perhaps cleanup/stop any database polling in the Component's componentWillUnmount. [...] This approach is not idiomatic for re-frame. Views are not imperative (they don't issue database queries), they simply render current application state.