Clojurians Log v2

Hi there 👋 Did something change in the way that Calva tries to find shadow-cljs.edn? It used to try and find it in one of the parent folders of the currently opened file. Now it seems to just look at the root of the opened workspace. For context: in our project the shadow-cljs.edn files does not live in the root, but in a subfolder.

I’m on 2.0.218 btw. The behavior seems to have changed in 2.0.217

In the 2.0.218 release notes it mentions that https://github.com/BetterThanTomorrow/calva/issues/821 fixed a problem around that, but the issue got reopened. https://github.com/BetterThanTomorrow/calva/pull/580 looks like it might bring general support for out of root project dirs, but it’s stale. We actually have 1 mono repo with 3 shadow-cljs.edn configs living in different directories, so one setting won’t be enough 😄

Yes, use 2.0.126 for now, we'll need to address this asap.

Hey, trying to get Calva working, and I keep running into a "No supported Jack-in project types detected." I'm using Leiningen. After doing lein new app temp, I have a project.clj file that looks like the following:

(defproject temp "0.1.0-SNAPSHOT"
  :description "FIXME: write description"
  :url "<http://example.com/FIXME>"
  :license {:name "Eclipse Public License"
            :url "<http://www.eclipse.org/legal/epl-v10.html>"}
  :dependencies [[org.clojure/clojure "1.8.0"]]
  :main ^:skip-aot temp.core
  :target-path "target/%s"
  :profiles {:uberjar {:aot :all}})

This sounds like https://github.com/BetterThanTomorrow/calva/issues/821

Try installing version 2.0.126 and see if it works for you. Jack-in for multi project directories is broken as of .127. I'm looking into it today

@yang.benjamin1998

Ok Calva friends, version https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.129 is out now, and fixes the jack-in issue for multi-project workspaces, as well as adds stack trace improvements! 🎊 Please report any issues.

You should now see stack traces like this in the output window. You can ctrl+click (cmd+click on Mac) the file names to navigate to the respective file+line.

You are a hero, @brandon.ringe!

You can also hover over the symbols in the stack trace to see symbol documentation as you can in normal editors, and ctrl+click (cmd+click on Mac) them to peek definition.

https://calva.io/output/#stack-traces Demo gif in the docs

Hi there. I have a problem with jacking-in. It gives me "Unable to resolve filesystem provider with relative file path 'c:\Apps\xyz-app/.calva/output-window/.clj-kondo'". Has anybody seen this?