go.nvim enables inlay_hints for all files (not just *.go) by default

[pcekm]

Just calling setup with defaults causes the plugin to enable inlay hints everywhere. This behavior is non-obvious, and tricky to disable if you don't know why it's happening. Simply calling vim.lsp.inlay_hints.enable(false) somewhere in your config won't do the job if it runs before this plugin gets set up.

My best guess is that this is a result of change 844b66b.

To reproduce, you need to set up a language server for a different language that supports inlay hints and edit a file in that language. I've reproduced it in Nvim 0.11.1 with dart files using dartls, and C++ files using clangd. In some cases the setting change occurs slightly after the first file is opened, which complicates things a bit. If at first you don't succeed, open a second file.

To work around this, disable inlay_hints in go.nvim. Something like:

require('go').setup {
     lsp_inlay_hints = { enable = false },
}

[alacine]

Diagnostics signs are not showing correctly either. I need to manually run `vim.diagnostic..config(local_lsp_config)` when open go file.

[szmktk]

I fully agree with @pcekm here. This is a very unexpected behavior and I lost quite some time trying to understand why I have inlay hints enabled (monkey-patching vim.lsp.inlay_hint.enable function with some print statements helped me to find the culprit). Installing a single plugin should not affect other plugins or the entire editor configuration.

[ray-x]

It’s a trade-off between configuring LSP behavior separately for each language vs keeping one unified setup. With the latest version of Neovim, it’s becoming difficult to promote special settings for gopls.
You can add an ft setup, but lazy setup can still cause issues.
I’m open to suggestions.

[szmktk]

I'm not aware of all the complexities you mentioned. But if I were to suggest anything I would always opt for configuring LSP behavior separately for each language.
Many developers work with multiple languages and would not like to keep separate configurations per language. A language-specific plugin should ideally only affect the behavior of that specific language, allowing developers to have fine-grained control over their LSP experience per language.

Would it be possible to scope go.nvim's inlay hint configuration to only affect Go files? This would follow the principle of least surprise and allow developers to configure each language's LSP behavior independently based on their preferences.
Thanks for all your work on this plugin!