onyx-platform
Provide an example
Hi, I'm trying out empathy, but each time I'm getting an error like
IllegalArgumentException No method in multimethod 'classify-error' for dispatch value: clojure.lang.LazySeq@3bc38c65 clojure.lang.MultiFn.getFn (MultiFn.java:156)
or
IllegalArgumentException No method in multimethod 'classify-error' for dispatch value: #{:thead :path :fieldset :aside :hr :meta :tbody :table :ul :nobr :script :button :use :strong :td :li :section :th :time :iframe :tr :article :legend :footer :header :tfoot :s :canvas :title :center :small :style :textarea :div :option :h4 :head :g :link :label :defs :svg :b :noscript :h2 :br :form :input :h1 :main :h3 :body :cite :rect :p :nav :i :img :a :select :html :span :u} clojure.lang.MultiFn.getFn (MultiFn.java:156)
It would be great to have a small working example in the README so it's easy to see what it actualy does.
Looks like we need to implement a bunch more error classifiers (especially LazySeq), and probably a default fallback one. We'll create an example. Thanks for the interest.
@plexus This is still WIP and depends on some changes that I'm lobbying for in core.spec. Will make a note in the README, didn't expect anyone to find this repo. :)
My fault. I pointed him to it, as there was some talk about spec's bad errors.
On 6 Jun 2016, at 5:53 AM, Michael Drogalis [email protected] wrote:
@plexus This is still WIP and depends on some changes that I'm lobbying for in core.spec. Will make a note in the README, didn't expect anyone to find this repo. :)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
I wish you all the luck! clojure.spec is a great opportunity to make the language more approachable, but with the current state of error messages it's really not helping much.
Thanks, we completely agree with the sad state of error messages and would like to be part of a push against this. We've focused on similarly better error messages within Onyx.