This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-28
Channels
- # aleph (50)
- # announcements (3)
- # aws (35)
- # beginners (74)
- # boot (25)
- # calva (39)
- # cider (18)
- # clara (2)
- # cljdoc (18)
- # cljs-dev (24)
- # cljsrn (11)
- # clojure (166)
- # clojure-europe (13)
- # clojure-italy (5)
- # clojure-nl (6)
- # clojure-spec (35)
- # clojure-uk (263)
- # clojurescript (22)
- # clojutre (1)
- # code-reviews (34)
- # cursive (58)
- # data-science (2)
- # datascript (4)
- # datomic (4)
- # duct (6)
- # emacs (7)
- # figwheel-main (9)
- # fulcro (2)
- # graphql (3)
- # hoplon (22)
- # hyperfiddle (2)
- # juxt (5)
- # kaocha (6)
- # leiningen (33)
- # luminus (15)
- # off-topic (1)
- # pedestal (5)
- # reagent (18)
- # reitit (12)
- # shadow-cljs (171)
- # vim (5)
Does anyone know of a REBL-like initiative for in the browser via cljs?
@thheller Nice, thanks 🙂
@U4YGF4NGM Thank you for sharing. I need to study it a bit. I'm mostly looking for a simple data inspector i can put in my devcards as a kind of debugger of the state of my application. Not sure if your work is built for that purpose?
something like https://github.com/Odinodin/data-frisk-reagent might be more what you're looking for
Hello, I have a reagent + re-frame question. Say I have a button that when clicked dispatches an event which updates the global db, and the re-render adds a "disabled" CSS class due to an operation being in progress. The intent is to prevent double clicks from causing an action to happen twice. To my understanding both the dispatch and re-render is async, so is it possible on an abnormally slow system to have two clicks / dispatches queued before the CSS class makes it un-interactable?
@raymond.w.ko you can still have some local state (a r/atom) if you need it
@raymond.w.ko you can try testing that by throttling your CPU in chrome devtools
Hello. How do you guys check security vulnerability for js modules? Since there is no package.json for usual cljs project, you can't really run npm audit
. Just curious how this could be done in efficient way.
otherwise you probably just can create a package.json
that includes the npm
versions of the cljsjs
packages you use?