This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-07-08
Channels
- # announcements (16)
- # beginners (22)
- # calva (3)
- # cider (17)
- # clojure (2)
- # clojure-berlin (1)
- # clojure-denmark (4)
- # clojure-dev (4)
- # clojure-europe (22)
- # clojure-madison (1)
- # clojure-nl (2)
- # clojure-norway (34)
- # clojure-sweden (3)
- # clojure-uk (3)
- # clojurescript (9)
- # datomic (7)
- # deps-new (1)
- # events (1)
- # fulcro (1)
- # hyperfiddle (10)
- # lsp (43)
- # missionary (1)
- # off-topic (27)
- # pedestal (10)
- # polylith (1)
- # reitit (4)
- # releases (1)
- # squint (18)
- # xtdb (8)
Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.463 • https://github.com/BetterThanTomorrow/calva/issues/2594 So, before this version Calva had a weird behaviour of loading the test namespace as it was saved on disk into the repl before running namespace tests. So you could evaluate some change (without saving the file) and then run namespace tests, and it would result in some saved code being loaded... We actually have ticked this change off as done two years ago, but we had missed an important case.
If anyone, for whatever reason, will miss the old behaviour, you can use runCommands
to create a keybinding that first loads the test namespace and then runs the tests. The two commands are:
1. calva.loadTestFileForCurrentNamespace
2. calva.runNamespaceTests
If I want to test the file on disk, I run the tests from the terminal. So, to speak for myself, I don't miss it.