This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-13
Channels
- # aleph (6)
- # architecture (29)
- # beginners (175)
- # cider (22)
- # clara (5)
- # cljdoc (5)
- # cljs-dev (28)
- # cljsrn (6)
- # clojure (62)
- # clojure-finland (7)
- # clojure-italy (7)
- # clojure-nl (2)
- # clojure-spec (23)
- # clojure-uk (194)
- # clojurescript (90)
- # core-async (2)
- # cursive (23)
- # datomic (41)
- # defnpodcast (2)
- # editors (4)
- # emacs (1)
- # figwheel-main (41)
- # fulcro (53)
- # hoplon (15)
- # hyperfiddle (4)
- # immutant (1)
- # jobs (7)
- # jobs-discuss (103)
- # lein-figwheel (9)
- # off-topic (34)
- # onyx (3)
- # parinfer (1)
- # portkey (1)
- # re-frame (7)
- # reagent (2)
- # remote-jobs (2)
- # rum (1)
- # shadow-cljs (148)
- # sql (54)
- # tools-deps (3)
- # vim (7)
Do there happen to be any plans to warn on ^{:deprecated "foo"}
vars (e.g. w/ a strikethrough as they do w/ Java)?
hrm in a multi-module project it doesn’t seem I can access the Deps tab? Leiningen tab comes up fine
@dnolen That can happen when the project is first created, if you close the project and re-open it will appear.
@potetm Not currently, but there should be. I’d like that myself for Java interop actually.
hrm what about paths that are “out of content root”? do I need to symlink to make the Deps stuff happy?
@dnolen Hmm, that won’t work at the moment, I can add that. I think symlinking would be the best for now, yeah. Are those paths shared across different projects?
@alexkeyes Probably not, at least not in the short term. I believe Midje is more or less abandoned, and it’s hard to support due to the number of macros it uses.
thanks for the response. it makes a lot of sense. We are trying to move back to clojure.test anyway.
I did try once and gave up, I have more useful macro support tools now so I could have another go but I don’t think many people use it any more so it’s unlikely to be a priority.
@p-himik I think in that case Cursive should resolve to both, but it’s possible there’s some weirdness there. When you say it highlights usages, do you mean the transient highlighting in the editor, or the Find Usages command?
I mean, sometimes it underlines them as errors, sometimes it does not. The error is "Incorrect arity".
That’s very strange. I assume your redefined functions use the same arities as the originals?
No, as I mentioned earlier: "The fix includes adding a signature to an already existing function."