LuaLS / LuaLS/lua-language-server

Go to Definition not working for class symbols inside inline function parameter types

Open
#3,399 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Lua
Stars
4.4k
Forks
442
PR merge metrics
No merged PRs in 30d

Description

### How are you using the lua-language-server?

Visual Studio Code Extension (sumneko.lua)

### Which OS are you using?

Windows

### What is the issue affecting?

Hover

### Expected Behaviour

Clicking on MyData inside the function(data: MyData) parameter list should navigate to the ---@class MyData definition, similar to how it works in a standard ---@type MyData

### Actual Behaviour

Hovering over MyData correctly displays the class documentation.

"Go to Definition" (F12) does not trigger any action.

No error is reported in the logs, it simply feels like the text is not "linkified".

### Reproduction steps

```lua
---@class MyData
---@field id number

---@param callback fun(data: MyData)
function Execute(callback)
end

-- Try to "Go to Definition" on `MyData` in the line below:
Execute(function(data)
-- The hover shows "(class) MyData", but F12 does nothing.
end)
```

Image

### Additional Notes

When a function parameter is annotated as a fun(arg: ClassName), the ClassName symbol in the hover tooltip shows the correct class information, but "Go to Definition" (F12 or Ctrl+Click) fails to navigate to the class definition.

Behaviors are normal in EmmyLua.

### Log File

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue in the Visual Studio Code Extension using the provided Lua example, then start at the F12 or Ctrl+Click go-to-definition entry point for MyData inside the fun(data: MyData) annotation. Compare it with the working hover behavior and standard ---@type MyData case. Done means the class symbol navigates to its ---@class MyData definition.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.