This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-28
Channels
- # announcements (1)
- # beginners (205)
- # calva (30)
- # cider (5)
- # cljdoc (25)
- # cljs-dev (2)
- # clojure (119)
- # clojure-brasil (5)
- # clojure-conj (7)
- # clojure-europe (2)
- # clojure-hamburg (7)
- # clojure-italy (14)
- # clojure-nl (2)
- # clojure-russia (13)
- # clojure-spec (79)
- # clojure-uk (58)
- # clojurescript (54)
- # core-logic (2)
- # core-matrix (2)
- # cursive (40)
- # datascript (2)
- # datomic (18)
- # duct (2)
- # emacs (14)
- # figwheel (3)
- # figwheel-main (7)
- # fulcro (30)
- # funcool (1)
- # graphql (10)
- # jobs (1)
- # juxt (13)
- # lumo (1)
- # mount (1)
- # off-topic (56)
- # other-languages (2)
- # pedestal (17)
- # powderkeg (2)
- # protorepl (2)
- # re-frame (10)
- # reagent (1)
- # reitit (7)
- # ring-swagger (10)
- # schema (2)
- # shadow-cljs (70)
- # spacemacs (13)
- # specter (4)
- # sql (9)
- # tools-deps (26)
I still believe you have enough info in the compilerException to make a red squiggly under the offending form.
Having said that, in Clojure 1.10, the error messages are much better and they relate to your code a lot better than before.
I will look for what I have there. In fact it seems Calva does not pick up enough about errors as it is, because sometimes it is just like nothing at all happens when you evaluate something.
It is pretty easy to get those red squigglys in place, it is just a matter of extracting the info. But do you mean you would want these squigglys when you evaluate something inline?
(defn delete-by-source-id! [datasource-store ctx source-id]
(->> {:source-id source-id}
(query-one! datasource-store ctx)
core/id
(delete! datasource-storex ctx)))
In emacs/Cider the form which is (delete! datasource-storex ctx)
is marked by a red squiggly, since datasource-storex
is not defined.
Can I ask for a new issue with just that suggestion? I don't know when I might have time to look at it, but it's good to have such issues for when I do have some times. They are fun. And also, maybe someone else finds it a fun feature to add.
A thing is that when you evaluate something, you really only give nrepl a chunk of code, so whoever is cooking the error messages can't really know about the file. But the file is a given anyway, so it is a matter of if you get the relative line and col and can work with that.
It used to be like that in Cider many years ago (that you only got the /tmp/blabla/line thingy
BTW do you want issues directly on Github or do you prefer to discuss them here first?
Oh, I don't know. I think it I'd like the issue on Github and then link pasted here. The discussions here vanish, which is sometimes a good thing, but most often I want to have the reference still there.