How to force all the projects in the workspace to appear when using Snack.picker.lsp_references()

[MichaelBitard]

I'm sorry, we cannot pinpoint what we are doing wrong here.

We have a typescript monorepo with 3 projects (in subfolders packages/api, packages/common, packages/ui), we use LazyVim with nvim 0.11.3.

We launch nvim and open a file in the common.
If we search references of a symbol in this file, it does not display references in packages/api or packages/ui, only in packages/common.
Where it gets weird, is that, if we open a file in packages/api, close the buffer, and search references of the same symbol, this time it finds this symbol in the common and the api.

We tried a bunch of stuff, including typescript project references, forcing the workspaces inside nvim-lspconfig but so far nothing works, except opening a file in each project.

We don't really understand the finder = "lsp_references", we have the feeling that something is configurable here, but maybe not.

We tried to force the nvim root_dir to 'cwd' too.

[drowning-cat]

Wait, are these mysterious "we" in the room too?

This code:

snacks.nvim/lua/snacks/picker/source/lsp/init.lua

Lines 392 to 403 in bc0630e

	---@param opts snacks.picker.lsp.references.Config
	---@type snacks.picker.finder
	function M.references(opts, ctx)
	opts = opts or {}
	return M.get_locations(
	"textDocument/references",
	vim.tbl_deep_extend("force", opts, {
	context = { includeDeclaration = opts.include_declaration },
	}),
	ctx.filter
	)
	end

Sends a request to the LSP server to get references. You can achieve the same with vim.lsp.buf.references(). If the results are the same, then the issue is likely with the LSP server itself.

Maybe the server requires a file to be opened before it registers the workspace. In that case, you can try sending didOpen request manually, as described in this blog post: https://artem.rocks/posts/workspace_diagnostics_nvim

Tip

Try to manually set workspace_files.

[drowning-cat]

Ideally, you should provide a repro. I suggest creating a github repository with the minimal tools and files required to demonstrate the issue, along with a README.md that contains the exact steps to reproduce. However, it will most likely be pointless.

You can also test whether the almighty VS Code behaves differently.

[MichaelBitard]

Haha sorry, yes, I use the "we" because we pair-program all day and we wrote this together...

VS Code has the same behavior 😱

We'll try a minimal repro, good idea!

[MichaelBitard]

Well, that was quite easy to put a repro example!

https://github.com/MichaelBitard/minimal_workspace_bug

Fails on nvim and vscode, tested on linux and macos.

Should I open a bug in vscode repo? 5000 opened issues 😱

[drowning-cat]

You can also use typescript-language-server. It should show references properly (not sure about any side effects though).

You did a good demo. I’d probably change the paths in the README.md to be root-related for easier understanding.

Should I open a bug in vscode repo? 5000 opened issues 😱

Don’t worry, in VS Code community they won’t bite you. Maybe they’ll show some settings that need to be enabled.