This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-20
Channels
- # aleph (11)
- # announcements (3)
- # babashka (35)
- # babashka-sci-dev (28)
- # beginners (29)
- # calva (51)
- # cider (33)
- # clj-kondo (26)
- # clj-on-windows (1)
- # clojure (40)
- # clojure-austin (1)
- # clojure-europe (47)
- # clojure-nl (9)
- # clojure-norway (7)
- # clojure-uk (5)
- # clojurescript (69)
- # conjure (30)
- # cursive (7)
- # data-science (9)
- # datomic (2)
- # etaoin (10)
- # events (2)
- # fulcro (1)
- # graalvm (1)
- # gratitude (6)
- # helix (16)
- # honeysql (20)
- # hyperfiddle (14)
- # inf-clojure (2)
- # jobs (1)
- # jobs-discuss (12)
- # kaocha (9)
- # leiningen (2)
- # lsp (4)
- # malli (8)
- # music (9)
- # off-topic (12)
- # pathom (10)
- # portal (14)
- # practicalli (15)
- # re-frame (27)
- # reitit (7)
- # remote-jobs (4)
- # sci (37)
- # shadow-cljs (16)
- # sql (8)
- # tools-deps (6)
- # vim (6)
- # xtdb (21)
Hi again 👋 In com.wsscode.pathom3.connect.runner-test/check-all-runners
I’m seeing that the inclusion of extra keys in a runner’s response doesn’t cause the test to fail. Is this by design?
Edit: After exploring a bit more, I see that there are additional keys included in runner’s response (such as entity data) so my hunch is it’s for that.
yeah, it uses matcher combinators library that does a check that allows for extra keys
there are ways to make strict, but most of the time its ok to let the extra keys
the nice thing is that it also allows for predicates in the middle of the structure, things like:
{:uuid (random-uuid)} => {:uuid uuid?}
are valid check definitions
I like to use this though another library called check
from @U3Y18N0UC: https://gitlab.com/mauricioszabo/check