2023-07-05 clojure-spec | Clojure Slack Archive

clojure-spec

MegaMatt 2023-07-05T20:14:49.258999Z

Wondering why this code produces the prn statements that it does.

(let [shape {:path1 true :path2 {:nested true}}
        path-exists? (fn [p o]
                       (let [p (map keyword (str/split p #"\."))
                             missing? (= :missing (get-in o p :missing))]
                         (prn o)
                         #_(not missing?)
                         true))]
    (s/def ::something (s/and (s/or :path1-exists (partial path-exists? "path1"))
                              (s/or :path2-exists (partial path-exists? "path2.nested"))
                              (s/or :path3-exists (partial path-exists? "path2.nested2"))))
    (s/valid? ::something {:path1 :here :path2 {:nested :here :nested2 :blah}}))

Res:

{:path1 :here, :path2 {:nested :here, :nested2 :blah}}
[:path1-exists {:path1 :here, :path2 {:nested :here, :nested2 :blah}}]
[:path2-exists [:path1-exists {:path1 :here, :path2 {:nested :here, :nested2 :blah}}]]

I’ll post the why i’m doing this in a thread in case others can suggest a better approach.

MegaMatt 2023-07-05T20:16:41.537489Z

I’m making a macro which takes a list of dot delimited strings and makes a spec which ensures the shape of the data eg. (defshape ["a.b.c", "a.d"]) would ensure you have something like

{:a {:b {:c "test"}} :d true}

MegaMatt 2023-07-05T20:17:18.634839Z

and sure, just s/and would work but the errors are not helpful to the developer thus i wanted s/or so that i can have a keyword that indicates the problem.

seancorfield 2023-07-05T20:25:01.110719Z

s/and is conforming, passing the conformed value into the second and subsequent specs.

seancorfield 2023-07-05T20:25:55.564899Z

I think if you wrap each s/or in s/nonconforming that will produce what you want.

MegaMatt 2023-07-05T20:26:16.029429Z

thank you.

MegaMatt 2023-07-05T20:46:03.126129Z

Update:point_up:: s/nonconforming solved my issue.

👍🏻 1

Clojurians Log v2

clojure-spec