Ben Brinckerhoff
Ben Brinckerhoff
Yes, it’s a bit tricky. Thanks for letting me know about your use case . It’s very helpful to know which cases need improvement. I’ll think more about this.
Ah, that’s a good idea, thanks!
@kelvinqian00 Thanks for posting this workaround! I agree this is not ideal. I’m thinking about ways to make this behavior optional.
@vemv Cool idea! I can definitely see how that output would the "evaluated from" output would be super useful. Let me think a little bit more about how this would...
@vemv One other thought - it might be worth filing a Clojure JIRA ticket about capturing this information more generally when a user calls `assert` (or, I suppose, during macro-expansion)....
Thanks a lot for your work on this! I haven’t made progress on this. Instead, my current focus in Expound is to think about how to let libraries like ‘utils.check’...
There isn't a clean way to do this currently, since code to print a value is currently independent of the type of failure (in this case, the failure type is...
@borkdude's was to write a custom value printer: ```clojure (declare my-expound-value-str) (def expound-opts {:show-valid-values? false :value-str-fn #'my-expound-value-str :print-specs? true}) (defn my-expound-value-str "Prints only keys if system map, else defaults to...
@drewverlee Thanks for the idea! I'll look into it.
@drewverlee Sorry for the delay here! I've had a bunch of other stuff going on. This is a cool idea, but AFAICT, the data that is passed to expound (the...