This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-07
Channels
- # adventofcode (40)
- # aws (15)
- # babashka (76)
- # beginners (39)
- # calva (6)
- # cider (3)
- # clj-kondo (3)
- # clojure (89)
- # clojure-austin (1)
- # clojure-australia (4)
- # clojure-europe (42)
- # clojure-italy (9)
- # clojure-nl (27)
- # clojure-spec (8)
- # clojure-uk (17)
- # clojurescript (9)
- # conjure (1)
- # data-science (1)
- # datomic (19)
- # deps-new (4)
- # docker (9)
- # emacs (5)
- # events (1)
- # fulcro (36)
- # kaocha (31)
- # lambdaisland (5)
- # leiningen (3)
- # membrane (3)
- # nrepl (10)
- # off-topic (31)
- # pedestal (7)
- # reveal (47)
- # shadow-cljs (35)
- # sql (9)
- # test-check (1)
- # tools-deps (24)
- # uncomplicate (12)
- # xtdb (5)
Hello! Is there a way to get list of keys from (s/keys...) ? And if I had few specs merged can I get back a full list of keys? If not, how do you do it? Thx
explain data approach - maybe but clojure.spec/form - doesn't work for merged spec thanks for links
both ways feels more hacky than just abstracting clojure.spec away and managing things by hands
For merged specs probably need to walk it doing s/form and s/registry. Walking datastructures ain’t hacky in a Lisp :op:
Well, I am simple guy and solved my problem with first creating entities as plain maps, later wrapping decision on what fields to use in 2 level multimethods, only from there creating spec, and returning it together with fields 🙂