yes thats right, Less plugin. I got it working eventually. Thank you though for replying ❤️

Dang. I was hoping for open extensibility. We wrap a lot of the re-frame API functions (as suggested by the re-frame docs) so the navigate to keyword would not work for our wrapped function.

So you should be able to use “Resolve as…” for that.

I’ll see if I can get the fix into the next build to allow that to be specified for any function, otherwise you can work around it by hacking a config file.

Oh cool. As long as there is some sort of hack to get it to work that would be awesome.

@cfleming oh, that. I think that’s a great way to do this. And actually, despite we are registering the defmethods with qualified keywords as dispatch values, the actual calls to defmulti are done with a map or such, so there isn’t (usually) a case that one need to navigate from the defmulti invocation parameter to the actual defmethod.

(defmulti kikka :type)

(defmethod kikka ::kukka [_])
(defmethod kikka ::kokko [_])

;; it's just a map, not a plain keyword, so no need to navigate from `kikka` to the actual implementation...
(let [m {:type ::kukka}]
  (kikka m))

thanks, all good 🙂

One could use identity instead of :type in the example, in case on could navigate from (kikka ::kukka) to the actual ::kukka defining defmethod but I think that’s not a common case.

Oh, I see - to navigate from the data itself to the multimethod impl handling that data.

Hmm

That actually might be quite nice, since you could use “Show implementation” to quickly see the handling code from a use of the data.