This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-12
Channels
- # adventofcode (1)
- # announcements (1)
- # atom-editor (4)
- # aws (4)
- # babashka (7)
- # beginners (46)
- # biff (14)
- # calva (11)
- # cljdoc (2)
- # clojure (78)
- # clojure-art (1)
- # clojure-austin (1)
- # clojure-europe (50)
- # clojure-nl (2)
- # clojure-norway (22)
- # clojure-spec (2)
- # clojure-uk (2)
- # clojurescript (72)
- # conjure (6)
- # core-typed (6)
- # eastwood (4)
- # events (1)
- # figwheel-main (11)
- # fulcro (1)
- # guix (1)
- # helix (13)
- # jobs (2)
- # jobs-discuss (4)
- # kaocha (2)
- # malli (5)
- # off-topic (7)
- # pathom (22)
- # pedestal (9)
- # re-frame (29)
- # reagent (7)
- # releases (2)
- # remote-jobs (1)
- # rewrite-clj (12)
- # shadow-cljs (44)
- # sql (13)
- # squint (2)
- # xtdb (17)
I'd like to catch parse errors and extract the location (row, column). Unfortunately, the ex-data
thrown in reader.cljc
only puts this information into the message.
I have a PR ready to add row
and col
to ex-data
, if you agree this is useful?
While looking into :row
and :col
(see above), I think I found a bug: When parsing this with ClojureScript:
(p/parse-string "(defn foo [)")
...I do not get ExceptionInfo
with a useful Unmatched delimiter
message like in Clojure, but: TypeError: Right-hand side of 'instanceof' is not an object
Yeah no, that was on me. Don't (catch Exception _)
in .cljc
files 😉
PR here: https://github.com/clj-commons/rewrite-clj/pull/181
I think the tests will not pass because of aforementioned issue with TypeError
in ClojureScript. I'm not sure if I can look into this right now and I think it is unrelated to my changes.
@fb seems like a good idea to me too! Thanks for thinking of it and taking a stab at it. I’ll take a peek at your PR sometime soon.
My pleasure! It was such a tiny contribution though 😄
Yes, I'm selfish. I no longer want to parse the exception message! 😛