This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-31
Channels
- # announcements (22)
- # asami (19)
- # aws-lambda (4)
- # babashka (42)
- # beginners (43)
- # calva (28)
- # cider (1)
- # clerk (79)
- # clj-kondo (12)
- # clojure (47)
- # clojure-berlin (1)
- # clojure-brasil (1)
- # clojure-dev (12)
- # clojure-europe (40)
- # clojure-nl (2)
- # clojure-norway (5)
- # clojure-uk (3)
- # clojurescript (56)
- # clr (12)
- # conjure (8)
- # cursive (4)
- # datomic (78)
- # dev-tooling (6)
- # exercism (1)
- # fulcro (9)
- # hoplon (3)
- # jobs (3)
- # jobs-discuss (4)
- # lambdaisland (3)
- # leiningen (1)
- # london-clojurians (1)
- # lsp (125)
- # malli (32)
- # matcher-combinators (3)
- # nrepl (1)
- # off-topic (6)
- # pathom (39)
- # re-frame (13)
- # releases (2)
- # remote-jobs (3)
- # sci (7)
- # shadow-cljs (117)
- # sql (6)
- # squint (7)
- # tools-build (15)
- # tools-deps (12)
Hello 👋
I’m seeing Subscribe was called outside of a reactive context
being logged a tonne, those warning seem to originate from re-pressed
(https://github.com/gadfly361/re-pressed/blob/b36e06023764f13baadc99e0dfebe4616c5f6a5c/src/main/re_pressed/impl.cljs#L180)
(is there a way to selectively suppress those warnings? any other suggested solutions?)
We are a bit behind the latest re-pressed
so apologies if that was fixed there, will update tomorrow to confirm—but looks like it’s not changed much compared to what we have
You could upvote this issue: https://github.com/day8/re-frame/pull/754
Sure thing! Do you know maybe how to handle situations when that warning originates from library code rather than application code?
@U7MHWDLD8 re-pressed was written before those warnings were added, so sorry for all the warnings! 😟 I am open to PRs if anyone here wants to submit a fix. I haven't used clojurescript in some time and not current on re-frame best practices anymore.
Hi @U0522BZ1R 🙂 No worries, that is of course 100% understandable! Just looking for a way to disable those for library code, I would think there should be a way 😉 🤞 We’re using re-pressed for https://nette.io/ so we might look into that if there is no other way
Looking at the implementation on the re-frame side (https://github.com/day8/re-frame/pull/752/files) seems like (set! re-frame.interop/reactive? (constantly true))
could work—but maybe there is better way?
`
I think that will cause a bug, but maybe you can use the re-frame.loggers namespace and remove one of the warning levels?