You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently custom symbol resolution supports following styles: def, let, for, -> and ->>.
It would be useful to also support defn style. It would work in cases like defcommand for Hystrix. Currently function (Hystrix command) arguments are not resolved and are shown as unresolved symbols in the args vector and function body.
+1 "Works like defn" is a very common macro pattern. I currently set these to "works like def" but the locals they define in the vector are still unresolved.
Interestingly, I was able to edit the config file where these are stored (IDEA_CONFIG_DIR/config/options/ClojureResolveSettings.xml) and change resolve-as to clojure.core/if-let, clojure.core/when-let, (I have two macros with the same shape as if-let and when-let) and clojure.core/defn and Cursive appears to understand correctly the binding and scope of the local vars my macros create.
@favila One thing to note with that hack - if you fiddle with that file and add a modification which requires indexing more vars (i.e. not just local bindings), you’ll need to do a File->Invalidate Caches.
Currently custom symbol resolution supports following styles:
def
,let
,for
,->
and->>
.It would be useful to also support
defn
style. It would work in cases likedefcommand
for Hystrix. Currently function (Hystrix command) arguments are not resolved and are shown as unresolved symbols in the args vector and function body.Example Hystrix function/command:
The text was updated successfully, but these errors were encountered: