This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-12-26
Channels
- # asami (2)
- # babashka (1)
- # beginners (31)
- # calva (11)
- # clj-together (3)
- # clojure (43)
- # clojure-europe (6)
- # clojure-norway (1)
- # clojurescript (14)
- # core-async (3)
- # core-logic (24)
- # cryogen (6)
- # datascript (2)
- # datomic (3)
- # fulcro (35)
- # honeysql (2)
- # hyperfiddle (12)
- # kaocha (3)
- # lsp (11)
- # off-topic (10)
- # pathom (2)
- # reagent (14)
- # releases (1)
- # sci (11)
- # shadow-cljs (27)
- # tools-deps (7)
• For the first one just press enter in the terminal where watch mode is running. • For the second one there's an open ticket and old poc PR. It's on the roadmap.
Ah, thank you. The first answer doesn't quite answer my question, though. Pressing return in the terminal only re-runs tests; it doesn't reload files. Also, if I am running watch mode from a REPL I don't have a terminal. My question was really about what happens when a file's timestamp changes and it has unchanged contents. In that case no reloading happens and tests don't re-run.
I've dug into the code a little. It turns out that this is the way Beholder works. The library Beholder uses under the covers, Directory Watcher, can be made to check only timestamps (and not file contents) as described at https://github.com/gmethvin/directory-watcher#configuration
I've dug into the code a little. It turns out that this is the way Beholder works. The library Beholder uses under the covers, Directory Watcher, can be made to check only timestamps (and not file contents) as described at https://github.com/gmethvin/directory-watcher#configuration