Please keep in mind that I have not yet used Inspectable, but my impression from reading the README is they both help developers understand spec-related failures.
Inspectable does this by providing rich, interactive UI that allows developers to explore the specifics of a spec failure at the REPL. This UI can be brought up at the REPL manually or you can set up a `caught` function to automatically open this UI upon instrumentation or macroexpand failures. Furthermore, Inspectable lets you explore specs interactively via `browse-spec`. On the other hand, Expound is a drop-in alternative for the string returned by by Spec in the case of failures. You can use this output wherever a human might read about a spec failure: in the REPL, in unit tests, in the browser console, in an error message for a REST API, and more. Since it is just static text, you can't interactively explore the failure or browse specs. Personally, I expect I'll use Inspectable during REPL-driven-development, but use Expound in my unit tests or when validating data that I consume from a 3rd party API. I hope that Juan Monetta (the author of Inspectable) will correct me if I've gotten anything wrong and add his perspective. Juan? Ben On Tuesday, July 25, 2017 at 6:12:21 PM UTC-6, Andy Fingerhut wrote: > > inspectable was recently announced in this group as well. Do you know > what the similarities and differences are between these projects? > > Andy > > On Tue, Jul 25, 2017 at 4:16 PM, Ben Brinckerhoff <bhbrinc...@gmail.com > <javascript:>> wrote: > >> Expound formats clojure.spec errors in a way that is optimized for humans >> to read. Expound works in Clojure and Clojurescript. >> >> This release provides human-optimized error messages when using a number >> of spec features, including instrumentation and `assert`. >> >> More information is available in the README >> <https://github.com/bhb/expound/blob/master/README.md>. >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clo...@googlegroups.com >> <javascript:> >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+u...@googlegroups.com <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+u...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
