@kenny That’s very strange. Does that happen for all namespaces requiring clojure.spec.alpha?

Yes that was the pattern. It fixed itself after I uncommented the :require.

That’s very weird.

No-one else has reported that - are you on IDEA 2017.3 EAP?

No. 1.6.2-eap2-2017.2.

Ok. In the latest EAP they’ve made some indexing changes, I thought that might have been the problem.

Though now that I'm back in the editor, navigation to re-frame keywords doesn't seem to work.

Oh, do they need to be full namespace qualified keyword? e.g. :foo/bar won't work but ::foo/bar will?

Seems to not work either way actually.

Ohh my bad. It's definitely because of the re-frame wrapper. Completely forgot about that. I believe you said there was a workaround for this?

Editing ClojureResolveSettings.xml?

Doing this does not work:

<item key="compute.ui-frontend.re-frame/reg-event-fx" resolves-as="re-frame.core/reg-event-fx" />

You might need to shut down IntelliJ, make that change and then re-start it

Tried restarting.

Ok, I’ll try to reproduce that on Monday.

Hi, I’ve been using cursive with unity and clojureCLJR and it’s working ok but I was wondering if anyone has tips. Like is it possible to tell cursive/intellij to turn off interop / classname inspections.

@snoe you can turn off most (all?) inspections at a pretty granular level in the preferences

@danielgrosse It seems the class/method highlights are at the syntax level not the inspection level - and I think the syntax level is all-or-nothing - I can’t seem to be able to keep clojure syntax and reference checks while turning off interop checks. Hopefully I’m wrong but if not I’m thinking the way to hack around the problem is to stub out java packages/classes/methods for the Unity stuff.

(I’m talking about these highlights if it wasn’t clear) https://imgur.com/a/EP9tk