This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-17
Channels
- # adventofcode (23)
- # announcements (2)
- # aws (11)
- # babashka (181)
- # beginners (59)
- # chestnut (2)
- # clj-kondo (9)
- # clojure (90)
- # clojure-brasil (2)
- # clojure-europe (18)
- # clojure-italy (24)
- # clojure-nl (9)
- # clojure-spec (3)
- # clojure-uk (28)
- # clojured (4)
- # clojuredesign-podcast (3)
- # clojurescript (12)
- # community-development (49)
- # core-async (49)
- # cryogen (5)
- # cursive (16)
- # data-science (1)
- # datascript (7)
- # datomic (54)
- # defnpodcast (4)
- # events (2)
- # figwheel-main (14)
- # fulcro (139)
- # graphql (1)
- # jobs-discuss (6)
- # kaocha (1)
- # luminus (2)
- # malli (3)
- # music (1)
- # off-topic (34)
- # pathom (24)
- # re-frame (13)
- # reitit (5)
- # shadow-cljs (8)
- # test-check (6)
I was mistaken--whenever I would make a change, like adding a println, figwheel would update my code and force a re-render, which would display the default values correctly, making it look like my change had fixed the code. If I did a page reload, it would regenerate the app-db and then re-generate the page, re-manifesting the bug.
The problem was that my multi-select options were coming from the server, meaning that the first time the multi-select rendered, there would be no default values. Then, when the default values arrived from the server, the component would not re-render, because React had cached it. Fix was to put a key on the parent component, and have the key change whenever the default values changed, which triggers a full re-render.
For people who use Firefox and would like the excellent cljs-devtools to work there as well, please go in and vote for this: https://bugzilla.mozilla.org/show_bug.cgi?id=1262914 as per https://github.com/binaryage/cljs-devtools/issues/40
The last time I’ve talked to Firefox DevTools team about custom formatters they had concerns about security and performance, don’t know what’s the state atm
sorry for the very specific question, is it possible to connect from calva to a remote cljs repl ? i've successfully connected to a remote clj repl using ssh port forwarding if i do the same with cljs i can connect the remote repl to my browser but id like to also connect with calva to the remote repl
Hi, I am using sente and when sending a large message from the client (a vector containing a few thousands of elements), sente fails and the message is not send. I get the following in the console:
backend.js:6 WARN [taoensso.sente:1065] - Chsk is closed: will try reconnect attempt (1) in 1162 ms
Should I send a few smaller messages? Or should I use transit to compress the message?
@guillermo I'm not in the know with these remote scenarios, but please ask that question in #calva-dev and hopefully we can get an answer. If it is not possible to connect, I'm super curious in what needs to be done in Calva to enable it. (I'm a Calva dev)
Testing transit now and it solves the problem with too large size. But I am getting stuck on transit UUIDs vs Clojurescript UUIDs (https://github.com/cognitect/transit-cljs/pull/10). How should I convert them to ClojureScript UUIDs with Sente directly?
Solved by
(sente-transit/get-transit-packer :json {} {:handlers {"u" uuid}})