PSA: If you use CLJS with fighweel in your project you might've noticed that "jump to definition" will jump into a weird figwheel-helper-deploy.js file. Eg when you jump to definition at (goog/getUid {}). You can exclude that JS file from indexing in "Open Module settings" (right click on your project), then Libraries -> figwheel-sidecar -> exclude -> choose compiled-utils.

@rauh Interesting, thanks - I might just exclude that file automatically in Cursive

@cfleming That'd be great 🙂

So, a few days ago the clojure resultion stopped working for me. One of my macros was acting as a defn, and Cursive was “doing the right thing” when I set it to resolve that as a defn. Now it isn’t working anymore, but the resolution is still set when I look at preferences. I tried invalidating cache/restart, clearing out the IDEA files and re-importing. No luck.

Ah, I see an open issue on github

@tony.kay Hmm, which issue looks like yours?

Oh, I see you’ve commented on one.

@cfleming Yeah, I’m having a number of issues. At the moment I’m trying an old release from Jan 1, and that isn’t working for me either. I’m going to try an old project and see if there isn’t something weird about what I’m working on. I’ve lost all ability to affect resolution of macros

I can give you a github project to look at if you care to

That’s very strange - the issue is I’ve never managed to reproduce this. If you could provide a repro project that would be excellent.

https://github.com/fulcrologic/fulcro

import, then open src/test/fulcro/client/mutations_spec.cljs

there is a macro called defmutation being used there

on line 14

won’t resolve

Ok, and you usually resolve that as defn?

yes

Ok, I’ll take a look when I get in.

ok, thanks!

@tony.kay ^^ (not sure if title mentions ping you or not)

yes

so, it won’t even offer it to me 😞

That’s not what you’re seeing?

it used to be. I don’t get the offer to resolve as defn…I’ve cleared all of them in prefs, but it still won’t reoffer

If you navigate from the defmutation symbol, does that take you to the macro definition?

Oh yea, the problems with qualified dependencies was fixed in 1.6.0 Thanks!

just a sec…opening it

yes, it does take me to the macro

but sample shows up in yellow

Whoa

All of a sudden, I’m seeing:

😕

I’m going to try an invalidate, one sec

That’s going to take a while, back with a cup of tea in a moment

k

I’ve gone as far as re-installing the plugin, clearing ~/Library (everything to do with IntelliJ), and git clean -xfd on the repo to clear out all IDE files.

Oh

Ok, this is a UI problem

Instead of opening the menu to the right, you have to select the Resolve… as… item with enter

oh, interesting

that works

For some reason, that confuses a lot of people (including me, from time to time), I think it’s the … at the end of the menu item.

weird that it had stopped working when I had it defined, though

Although looking at the popup, JetBrains do the same for the Typo inspection.

let me look at the other project that was having problems…

yeah, seems ok now

Great

I’m not sure how to make it clearer in that popup what the user needs to do.

So, the resolution had stopped working at some point with the resolution still in prefs, but now that I’ve reinstalled everything hard to know what was causing that

Yeah, for sure. Ok, well let me know if you have more problems.

thanks, I appreciate your time

If you see it again let me know before you wipe everything, and we’ll see if we can debug it.

k, will do

@hlship The copy reference thing? Yes indeed!