is there a way to spec map's key+value, but the key isn't specific

like how do I say: map key is symbol or keyword, if key is symbol then value must be string but if key is keyword then value must be integer

I tried s/coll-of :kind map? but that only conforms value

Is this useful to you perhaps? https://clojure.github.io/spec.alpha/clojure.spec.alpha-api.html#clojure.spec.alpha/map-of

@roklenarcic

@roklenarcic can the map also have combinations of these key/val pairs?

in that case I would make a spec for the map-entry

You can use s/every with an s/or of s/tuple for entry combinations

Self-hosted cljs with spec in the browser: https://twitter.com/borkdude/status/1059758785613479937

thank you alex, I'll try that

hm well every doesn't conform

hm... when using coll-of, if I specify kind as map? and if I don't specify kind, conforming works differently 😄

@roklenarcic specify it as a seq of tuples?

so something like (coll-of ::my-tuple-spec)

tuple spec is no better than map-of spec... each item is independent

::my-tuple-spec can spec independent things?

(s/tuple pred1 pred2)

you can't link type of 1 and type of 2

(s/or (s/tuple symbol? string?) (s/tuple s/keyword? int?))

so s/coll-of that?

yes

and I guess :kind could optionally also be set to map?, it’s just an extra check

(s/conform (s/coll-of (s/or :s1 (s/tuple symbol? string?) :s2 (s/tuple keyword? int?))) '{a "A" :b 3})
=> {:s1 [a "A"], :s2 [:b 3]}

but often a seq of map-entries can be used in places where maps are used

this is completely different to how I would expect things to go

I would expect a collection of tuples

@roklenarcic you mean the conformed value?

yes

this looks completely wrong and unexpected to me

it isn’t wrong, it’s conformed. else you get ::s/invalid

(s/conform (s/coll-of (s/or :s1 (s/tuple symbol? string?) :s2 (s/tuple keyword? int?))) '{a "A" :b 3 c "B"})
=> {:s1 [c "B"], :s2 [:b 3]}

see... now I lost a term

input map has 3 key-values

result has two items

ah I see

so maybe every will help there?

nah, I'll just switch back

to :kind map?

and take vals

problem solved

if I had time I would help you figure it out, but I have to go now

don't worry, I have a solution, I was just looking for something more elegant

yes, (s/conform (s/every (s/or :s1 (s/tuple symbol? string?) :s2 (s/tuple keyword? int?))) '{a "A" :b 3 c "B"}) works

every doesn't do any conforming at all FYI

at least I think so

oh you want conforming

sorry 🙂

(s/coll-of x :kind map?), conforms key+value into value

so you just have to take (vals ) of value in the map then

@roklenarcic

(s/conform (s/cat :map-entries (s/* (s/alt :s1 (s/tuple symbol? string?) :s2 (s/tuple keyword? int?)))) '{a "A" :b 3 c "B"})

well that's clever 🙂

I'm having some problems adding :args specs to a function, I think it kind of boils down to this:

(spec/def ::title string?)
(spec/def ::entry-x (spec/cat :title ::title))
(spec/valid? ::entry-x ["Title"])                     ; => true
(spec/valid? (spec/cat :entry ::entry-x) ["Title"])   ; => true
(spec/valid? (spec/cat :entry ::entry-x) [["Title"]]) ; => false

I guess you can nest s/cat?

(s/def ::foo (s/cat :a int? :bcat (s/cat :b int?)))
(s/conform ::foo [1 2]) ;; {:a 1, :bcat {:b 2}}

regex ops nest to describe the same structured collection

if you need a new “level”, insert s/spec

Interesting I would have expected that spec to match [1 [2]] I guess

this is covered in the spec guide

it behaves the same as s/alt, s/*, etc. they consume the same seq “level”

Ok, s/spec did the trick. Also found the section in the spec guide now

@roklenarcic please watch the thread, Alex gave some advice there

btw, handy link if you quickly want to check examples posted here: http://app.klipse.tech/?cljs_in=(require%20%27[clojure.spec.alpha%20:as%20s])

is this feature in clojure 1.10 related to upcoming changes in clojure.spec maybe? https://twitter.com/timbaldridge/status/1059815352106795008

what is instance based protocol polymorphism?

type vs instance

number vs 42

in short you could have a custom impl of some protocol fn bound to a value (via metadata) instead of a type

in clojurescript this is like specify!

well the number mention is not a good example 🙂 no meta

cant you dispatch now based on meta?

sorry for being annoying, but I am very curriuos about it 🙂

(defprotocol Foo (foo [x])) (foo (with-meta [42] {`foo (fn [x] :boo)})) -> :boo

https://github.com/clojure/clojure/blob/master/changes.md#22-protocol-extension-by-metadata

i will have a look, thanks!

super cool feature (not really related to spec tho, as far as we know)

well, I thought, maybe this way predicates could be bound to keywords and spec could use that

keywords do not support meta I believe

ah

they don't, this is ~ specify limited to IObjs (modulo the different method resolution rules around direct impl)

satisfies? doesn't work with the new "instance-based polymorphism"?

apparently not

no, I was looking at a related fix for CLJ-1814 but I think somebody should make a ticket just for this specific issue

^^ yes, please.

Ok, I can do it.

Hi, I'm trying to get a feel for where to 'draw the line' on more dynamic behavior in specs. I've created an EDN based data description language for one of my projects. I have it spec'ed out pretty thoroughly, but I have a situation where I have say :data/type that could be one of a fixed set of types (:string :long, etc) or a type that's defined elsewhere in the larger data structure I'm validating. my code is already doing some additional validation based on core.logic etc once the definitions are loaded. So just wondering if it's better to defer this type of check to that point

Is there an equivalent of ns-unmap for a symbol you used spec/def on? (I suspect this question will reveal an error in my mental model of how symbols and specs relate)

Just s/def it to nil

🆒 thanks!

If I remember correctly

yes