Oliver George
Oliver George
Perhaps this could result in a better `enable-console-print!`
That partially solves the "string with metadata" issue. ```cljs cljs.user=> (defn data-str [data] (binding [*print-level* 3 *print-length* 5] (specify! (js/String. (pr-str data)) IMeta (-meta [_] data)))) cljs.user=> (data-str {:a (range...
This is the best I've come up with ```cljs (defn log-data [& data] (binding [*print-level* 3 *print-length* 5] (let [s (apply pr-str data) d (specify! #js [] IMeta (-meta [_]...
That sounds like a good approach. I guess the other possibility is to extend IFormat for ExceptionInfo and use ex-data to enable special treatment.
Interesting. Thanks. (I'd love to know what Bruce is thinking about presenting spec errors. Can't help but think he'll be the trendsetter.)
Thanks Bruce. That approach could be quite inconvenient depending on how the server side is setup. It would require two server side templates, different urls and other config. I wonder...
Perhaps it's worth updating the README to make this explicit. I found this quite confusing... was doubting my setup when the problem was I needed to change a file to...
Happy to help out with some test cases too. Bit of a can of worms really - there are quite a lot of cases to consider.
Hello My turn to apologise for slow response. Very happy to do that but I am quite busy myself right now. I'll see how I go - let's keep in...
#203 sounds similar but the patch doesn't help - code it changes isn't used (based on some basic logging)