This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-29
Channels
- # babashka (4)
- # babashka-sci-dev (96)
- # beginners (79)
- # calva (26)
- # cider (5)
- # clerk (2)
- # clj-kondo (23)
- # clojars (14)
- # clojure (54)
- # clojure-europe (8)
- # clojure-sweden (3)
- # clojurescript (76)
- # datomic (12)
- # deps-new (6)
- # emacs (20)
- # events (3)
- # exercism (1)
- # fulcro (11)
- # funcool (12)
- # hugsql (14)
- # hyperfiddle (6)
- # kaocha (1)
- # lambdaisland (1)
- # lsp (22)
- # malli (1)
- # matcher-combinators (6)
- # nbb (6)
- # off-topic (128)
- # polylith (14)
- # re-frame (4)
- # reagent (1)
- # releases (4)
- # shadow-cljs (8)
- # tools-build (13)
- # tools-deps (13)
- # tree-sitter (5)
In CIDER, when an is comparing two maps fails I get a diff report between the two Is there something similar which walks the combinators and reports the errors structurally?
do you mean you only want to see the differences and leave out all other data or have it elided with ..
? Maybe some screenshots of what CIDER does in this case would help me understand what it does
nice, thanks!
This doesn't exist in matcher-combinators but it could probably be added fairly easily and then there could be a configured of how the test failure passed to clojure.test
.
Alternatively one could wrap the test runner that displays the clojure.test results to do such a traversal (like as a tool outside of the lib itself)
I can try to play with it a little sometime soon