Fork me on GitHub
#cursive
<
2024-01-25
>
cfleming04:01:45

Cursive 1.13.2-eap3 is out now, fixing two issues: one with deps, where relevant maven repositories weren’t being correctly registered with IntelliJ, and another where the UI would freeze when modifying a test namespace while the tests from that namespace were running: https://groups.google.com/g/cursive/c/YbikbBgQ4tg/m/F8uUgbyKAQAJ

genekim05:01:36

🎉🎉🎉. Thank you!!!

imre10:01:53

Thanks @U0567Q30W, that indeed did it (needed a Refresh Clojure Deps Projects to trigger the indexing)

imre10:01:26

Once the functionality was restored I checked my repo list in the project and noticed the Clojars index was from November last year I think

imre10:01:01

Is there any way to periodically refresh the repos, or is this something I need to do by hand project by project?

p-himik20:01:28

Just opened an older project of mine that I haven't touched after upgrading Cursive for the first time in a couple of years. Seems that :require-macros in CLJS files has stopped working properly in terms of resolution? Same with :refer-clojure and, for some reason, requiring clojure.string, see the pic. Perhaps relevant to https://github.com/cursive-ide/cursive/issues/2779 but no clue. Tried invalidating the cache and updating to the latest EAP - no dice. Any suggestions?

cfleming21:01:09

I don’t think anything there has changed in a long time. Any spec error definitely comes from Clojure/CLJS itself, Cursive doesn’t use spec at all.

cfleming21:01:18

I’ll try to reproduce and see what I can see.

p-himik21:01:25

Yeah, I don't know how to get to the spec error itself, so no clue whether the issue is really relevant to what I'm seeing.

p-himik21:01:05

Just to clarify - defcomponent is a macro defined in a CLJ file with the same namespace. Its usages in the CLJS file are properly resolved, but it's still marked as not being used - the tooltip on that grayed out line is "Unused require". The first line says "list cannot be resolved". The third line says "string cannot be resolved". Not sure how relevant, but goog.object also can't be resolved.

cfleming21:01:38

Hmm, ok, I’ll try to set that up and check it out.

onetom16:01:11

the https://plugins.jetbrains.com/plugin/18108-clojure-extras plugin also underlines issues and it has nothing to do with Cursive. but in this case it seems those underlines are indeed related to Cursive, if u r having resolution issues. is it a deps or a lein project? also, since u haven't opened this for a long time, is it possible that you are still using unqualified symbols as artifact names, like nrepl instead of nrepl/nrepl?

p-himik16:01:14

I don't use the extras plugin, and the project is deps-based. No unqualified symbols, unless they're :refered to.

onetom16:01:42

unqualified artifact names in the deps.edn

p-himik19:01:36

No. And how could that be relevant, given that the errors come from my own namespaces?