Log entries for auto-detected libraries could indicate how they were detected

[adam12]

I have checked that this feature is not already implemented

• This feature does not exist

Use case

When trying to debug why a certain library was detected (ie. Rubocop) it would be nice to indicate how the detection happened.

Description

When starting ruby-lsp in a project, I encountered the following log entries:

[2025-11-28 20:29:40] [LOG] Auto detected formatter: rubocop_internal
[2025-11-28 20:29:40] [LOG] Auto detected linters: rubocop_internal
[2025-11-28 20:29:40] [LOG] Detected test library: rails
[2025-11-28 20:29:40] [LOG] Ruby LSP detected this is a Sorbet project and will defer to the Sorbet LSP for some functionality

The problem is that none of these are true. The project doesn't use Rubocop (albeit not directly), nor does it use Sorbet.

I actually don't think this is a problem in ruby-lsp. I use a small shim script to run my local fork correctly and I assume that it's detecting some of these as the ruby-lsp project.

But it would be great to know why they were detected. ie.

Auto detected formatter: rubocop_internal (presence of rubocop.yml in project root)

Implementation

No response

[egiurleo]

Hi, @adam12! Thanks so much for opening this issue. We really like this idea. If you have the capacity, we'd be happy to review a PR implementing this feature.