This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-04
Channels
- # announcements (5)
- # aws (11)
- # babashka (15)
- # beginners (101)
- # biff (14)
- # calva (45)
- # clj-kondo (18)
- # cljs-dev (5)
- # clojure (178)
- # clojure-austin (5)
- # clojure-europe (8)
- # clojure-france (1)
- # clojure-nl (12)
- # clojure-norway (6)
- # clojure-spec (4)
- # clojure-uk (1)
- # clojurescript (13)
- # community-development (2)
- # conjure (6)
- # cursive (8)
- # datahike (1)
- # datalevin (3)
- # datascript (36)
- # datomic (6)
- # emacs (2)
- # etaoin (2)
- # fulcro (5)
- # graalvm (6)
- # gratitude (3)
- # introduce-yourself (1)
- # jobs-discuss (1)
- # lsp (19)
- # malli (4)
- # nbb (11)
- # off-topic (4)
- # other-languages (1)
- # pathom (19)
- # pedestal (1)
- # shadow-cljs (22)
- # spacemacs (16)
- # tools-deps (31)
- # vim (7)
I'm having a weird issue where parinfer-rust isn't working at all in one specific file/namespace, but works fine in all other files I've tried. It's a .cljc
file but I don't think that's an issue issue since it works in other .cljc
files. Anyone have any tips for debugging this kind of thing?
Are there existing errors in the file? It might be struggling to parse the file correctly
Ah, yeah, I figured it out (just found out that you can set a logfile location). There were unbalanced double quotes in a comment which apparently causes an exception to be thrown while parsing. Seems odd that that totally breaks the plugin without explanation
Ah, and that also happens to be the most recently-filed issue: https://github.com/eraserhd/parinfer-rust/issues/128
I had this exact problem recently! https://clojurians.slack.com/archives/C0DF8R51A/p1658175219462129