This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-21
Channels
- # beginners (25)
- # cljsrn (3)
- # clojars (4)
- # clojure (37)
- # clojure-news (1)
- # clojure-poland (2)
- # clojure-uk (6)
- # clojurescript (9)
- # datomic (2)
- # duct (7)
- # fulcro (2)
- # hoplon (3)
- # jobs (1)
- # keechma (1)
- # luminus (1)
- # off-topic (27)
- # om (3)
- # om-next (2)
- # overtone (4)
- # pedestal (2)
- # re-frame (11)
- # reagent (4)
- # reitit (6)
- # rum (2)
- # shadow-cljs (212)
- # slack-help (3)
- # spacemacs (1)
- # sql (1)
- # test-check (32)
- # tools-deps (1)
@shaun-mahood remember to use the to repl
part too
https://github.com/Day8/re-frame-10x/blob/master/docs/HyperlinkedInformation/UsingTheRepl.md
@mikethompson I found it (must be good UI design because I wasn't looking), it's pretty great! Strangely looking forward to work on Monday (as if I won't be dragged away from my computer for a meeting or something) :)
It's bad form to store a DOM element ref in db
since DOM elements are mutable, right?
is there a way to break an interceptor chain? return false from the :before
function or something? this would be for something like you don't have permissions to see this view
or somesuch...
@hoopes can't interceptors modify the context, which includes other interceptors?
ctrl+f A context is a map with this structure:
here: https://github.com/Day8/re-frame/blob/master/docs/Interceptors.md
@lgessler that would depend on your concrete usecase but with React, DOM elements are destroyed all the time
In this particular case, I know that the DOM element in question would persist for as long as I would be accessing that part of db
, but this still feels like not the cleanest solution