This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-06
Channels
- # babashka (62)
- # beginners (52)
- # calva (37)
- # clj-kondo (23)
- # cljs-dev (13)
- # clojure (18)
- # clojure-europe (7)
- # clojure-sg (1)
- # clojure-spec (27)
- # clojurescript (37)
- # datomic (14)
- # events (2)
- # fulcro (9)
- # graalvm (12)
- # helix (1)
- # introduce-yourself (1)
- # keyboards (3)
- # lsp (3)
- # missionary (24)
- # nextjournal (7)
- # pedestal (3)
- # polylith (15)
- # re-frame (5)
- # reitit (4)
- # releases (2)
- # shadow-cljs (54)
- # testing (7)
- # uncomplicate (4)
Hi, I'm following the tutorial here https://day8.github.io/re-frame/dominoes-live/#the-view-functions and noticed that although most live code snippets seem to work, at the chapter The View Functions the [clock] snippet breaks on first load: "Execution error. ERROR: TypeError: Cannot read properties of null (reading 'toTimeString')". This doesn't seem to happen for any other snippets, even similar ones like [color-input] and [url]. When I make a trivial change to the code for defn clock (like adding some whitespace), the snippets rerender and the clock is correctly displayed below the error. Just thought I'd post this here, wasn't sure whether a bug report on the repo would be appropriate for docs like this.
Maybe replacing -> by some-> in defn clock fixes it? It would prevent the error at least I think, but not sure whether it will rerender by itself after that
I cloned the repo to try that out, but klipse doesn't seem to work when I run the docs locally (404 for js files)
The time subscription is returning nil the first time. The db is probably not being initialized (via the :initialize event) before that clock component is rendered. Using some-> would avoid the error thrown in the component, but it doesn't solve the underlying problem.
The problem in the example is that the db is not initialized until after the clock component above is rendered.
https://day8.github.io/re-frame/dominoes-live/#kick-starting-the-app
If the call to (rf/dispatch-sync [:initialize]) was done before the clock component you wouldn't see this problem. That may be a suggestion to make in a bug report.