`defmsg` only works for some types of specs about expound HOT 8 CLOSED

The suggestion, to wrap the set as #(contains? #{1 2 3} %) does work.

from expound.

Related: #96 - this would allow users to add messages to existing spec messages (or overwrite them completely)

from expound.

If this could be made to work, it would be akin to a game changer. But even for something as simple as this:

(s/def ::id (s/or :idint ::id-int :idstg ::id-stg))
(ex/defmsg ::id "Should be either an integer or string of digits")
(ex/expound ::id "abc")

You just get the 'standard' error

Also, trying to use the 'fix' of #96 does not work either:

(ex/def ::id (s/or :idint ::id-int :idstg ::id-stg) "Should be either an integer or string of digits")
(ex/expound ::id "abc")

Just results in standard error.

So, should I give up on this?

from expound.

@jsa-aerial Thanks for using Expound! Unfortunately, you're correct: there isn't currently a way to add messages for compound specs like the example you posted above. It's on my radar, but probably won't take priority over some other areas (like spec.alpha2 compatibility) in the immediate future.

from expound.

OK, in any event, I actually am wanting 'end user' type messages. And that actually doesn't look to be in the scope of Expound anyway. So, may as well close this.

from expound.

That’s correct. Expound is focused on messages for developers. Perhaps Phrase would be a better fit here? https://github.com/alexanderkiel/phrase

from expound.

Yeah, I was looking at that last night before I replied here. It looks to be 'on the right track", but is totally opaque on how / where / why the dispatch mechanism is tied into your specs. It works for the simple toy examples given, but does not work at all for even a simple 'or' spec. Or at least it defeated me in getting it to work over the course of many permutations...

from expound.

This has been fixed as of 2c4019f

from expound.