Navigate between files using namespace names

[markaddleman]

In Cursive, you can navigate among files by using their namespace names rather than munged directory names. For example, I could navigate to library.test-utils instead of library/test_utils. It's a small thing but it helps to reduce context switching

[bpringe]

This could probably be implemented as a custom command that prompts for a namespace, finds the associated file in the project directory, and opens it in an editor.

[bpringe]

@markaddleman Is this done statically in Cursive (can you navigate like that without a repl connection)?

[markaddleman]

Yes

[bpringe]

@ericdallo, can and should this be implemented in clojure-lsp?

[PEZ]

I'm thinking on when this would actually be needed much:

1. When typing in the file browser you can just skip typing the dots and dashes and you will find the file pretty easily.
2. If it is a namespace in a Clojure file, you can navigate to it (e.g. cmd/ctrl-click).
3. If it is that you have it some other file and want to paste it, well, I just made an extension that can help with that, and added an example for this use case: https://marketplace.visualstudio.com/items?itemName=betterthantomorrow.paste-replaced

Is there some base not covered by these? A demo gif of how its done in Cursive would be nice!

[ericdallo]

A demo gif of how its done in Cursive would be nice!

Yeah, that would certainly help, I can't easily see how that would work

[bpringe]

@markaddleman Is this what you were referring to? (Taken from here.)

Regarding what @PEZ said, it seems we are not lacking in options for navigation. In any case though, I think some clarification would be helpful on what is being requested exactly.

[ericdallo]

@bpringe if so, this already works via the workspace/symbol request, this is an example using lsp-mode lsp-ivy-workspace-symbol

[markaddleman]

@markaddleman Is this what you were referring to? (Taken from here.)

Regarding what @PEZ said, it seems we are not lacking in options for navigation. In any case though, I think some clarification would be helpful on what is being requested exactly.

Yes, this is what I was thinking. Navigating namespaces by clicking through references in source files is also ab important feature for me

[ericdallo]

@bpringe that is already possible to be implemented as I showed before, let me know if have any questions about how lsp-mode works for that.

Navigating namespaces by clicking through references in source files is also ab important feature for me

This is a LSP protocol limitation, the lenses click/action only allows to execute a Command, not offer a feedback to user showing the references or something like that, I need to investigate that further more to see if there any other choices/workarounds

[mrkam2]

I'm adding my voice to this feature. The scenario I need this the most often is when going from test execution logs and stacktraces to the code. Unfortunately, these often feature namespace names rather than complete file paths.

Stacktrace example:

              compojure.core$wrap_response$fn__18493.invoke (core.clj:158)

This line only specifies the file name which is quite generic, so you need to use the namespace name to jump to the correct file.

Test log example:

Testing reporter.reports-test

This one only has the namespace.

@PEZ implemented a really cool workaround for this, which is altering paste operation to replace certain characters. I was able to configure it to work really nicely with one caveat that it still requires you to double-check the match as it could choose a different one because of the recency or other artifacts of search results sorting. See the discussion in slack.

[ericdallo]

@bpringe I just added the support for clicking on references code lens for emacs/lsp-mode here, Unfortunately, it's something that must be done for every client, handle that command and show call the references from the command args.
I suggest you create a new issue on Calva to add that support

[bpringe]

@ericdallo I may be misunderstanding what you mean, but I think Calva has this feature already. We can click the references code lens and see the references and click them.