What's a good way to kind of namespace specs internal to a file? So the issue is that s/keys needs to have a spec named, say foo

So I would do ::foo. However, my function returns a modified map, hence the :ret also has to be something that has s/keys with ::foo

And many functions in that file return modified maps

So I kind of want to namespace the spec for this function

I'm now doing :function-name-pre/foo

Anyone has a better solution?

do you need qualified keys in the map? or are you going to have multiple */foo keys?

if not, why not use unqualified keys?

or maybe I misunderstand the question

The s/keys already spec it as unqualified

Because of that

The actual key has to have a name that matches the key in the map that is specced

sorry, not sure I understand what the question is then

Thanks! Haha

Maybe in short it's "how do you group specs for a function?"

@ackerleytng I'm not sure I understand the problem you think you have... why does :ret come into this and cause you a problem?

Perhaps if you shared a concrete example?

Sure hmm I'll work one out and post it later

is ::s/invalid part of the public api?

I don't believe so but there's a function s/invalid? you can use to test for that value.

(that said, I've written conforming predicates that return either an updated value or ::s/invalid a few times so...)

I have a spec that checks that one of the keys is a core.async channel; I’d like to write a custom generator for that specific key spec, but I can’t seem to determine how to write a generator that returns a channel; I feel like I’m missing something obvious here

thanks @seancorfield

yes, ::s/invalid is part of the public api @bja @seancorfield

Thanks for the clarification @alexmiller!

I’ve created a new channel for expound-related questions - #expound