This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-11
Channels
- # announcements (16)
- # architecture (1)
- # babashka (24)
- # beginners (49)
- # biff (5)
- # calva (13)
- # clerk (3)
- # clj-kondo (4)
- # clojure (46)
- # clojure-dev (1)
- # clojure-europe (22)
- # clojure-losangeles (5)
- # clojure-nl (1)
- # clojure-norway (15)
- # clojure-uk (2)
- # clojurescript (28)
- # code-reviews (2)
- # community-development (6)
- # conjure (10)
- # cursive (8)
- # datalevin (15)
- # datomic (32)
- # events (1)
- # fulcro (9)
- # hyperfiddle (32)
- # introduce-yourself (1)
- # lsp (27)
- # malli (1)
- # matrix (3)
- # missionary (6)
- # off-topic (24)
- # practicalli (2)
- # rdf (1)
- # re-frame (7)
- # reagent (10)
- # reitit (5)
- # rewrite-clj (9)
- # sci (6)
- # scittle (4)
- # shadow-cljs (23)
- # tools-deps (74)
- # vim (19)
- # xtdb (5)
If I have a function that derefs a subscription but also renders a component deref-ing the subscription in a reaction (and disposing the reaction on unmount), does this still present a problem with memory leaks? I want to say no, but I want a second pair of eyes to review this logic.
Unfortunately rf/subscribe
will still warn me about calling outside of a reactive context (which I can totally understand, because my use case is extremely subtle), but I feel uncomfortable using with-redefs
to surpress the warning in this case
I wrote a wrapper for subscribe
for a similar use-case that uses the cache read-only and doesn't emit the warning - works just fine. :)
I think I have asked this question here, but anyways, I will link it. I'm having issues making HTTP requests to work, with http-fx. Could anyone give me a hand? Maybe I'm doing something trivially wrong. https://clojurians.slack.com/archives/C03S1L9DN/p1683826681240629
Have you printed (console) your ur and is to see if they are really showing up as expected?