Class methods vs fields with function values

[TracerDS]

You can set class fields with ---@field annotation.
However when you use that on methods, the LSP treats the field as a variable that has a function as its value instead of the variable being a method itself.
Is there a way to differentiate between these two or not really?

---@class MyClass
---@field MyFunction fun(): number

The icon should be marked as a method. Instead it is marked as a field/variable

[tomlau10]

AFAIK, @field are mainly used for member fields but not class functions / methods.
You need to write it using setfield / setmethod style for LuaLS to treat it as a class function / method 🤔

---@class MyClass
local cls = {}

---@return number
function cls.MyFunction()
    return 1
end

---@return number
function cls:MyMethod()
    return 2
end

cls. -- try trigger completion here

[TracerDS]

Adding --- @class RecordClass to the methods object didnt change anything sadly.
It still treats them as field and not methods :/

[tomlau10]

Adding --- @class RecordClass to the methods object didnt change anything sadly.
It still treats them as field and not methods :/

but did you remove your ---@field MyFunction fun(): number first?
you need to remove those @field lines, because they take the highest priority

and can you try my minimal demo code above, to verify if the completion show Delete / GetName / SetName as methods?

[TracerDS]

I cannot remove the ---@field lines as without them I dont even have intellisense in the first place (for the class methods)

I tried ur minimal example, sadly the same thing happens.

[tomlau10]

I cannot remove the ---@field lines as without them I dont even have intellisense in the first place (for the class methods)

• If you added the @class correctly on the table that defines your methods, you don't need @field at the beginning.
• If you dont have intellisense after adding @class and removing @field, then I believe you added the @class incorrectly.
• And since @field takes higher priority, if at the same time you have @field GetName fun():..., then even if you add @class correctly on the methods table, you will still see GetName as a field but not method.

I tried ur minimal example, sadly the same thing happens.

I wonder if you just put my minimal example into your existing workspace ? 🤨
And since your workspace already have a RecordType class, with some @field GetName fun()... or so
=> when you trigger completion in my demo it still treats it as a field but not method

---

I just constructed another minimal example
with some class name that should never collide with your existing ones

local MyTestClass = {}

---@class MyTestClass
local MyTestClassMethods = {}

--- @return MyTestClass
function MyTestClass.new()
    return {}
end

function MyTestClassMethods:Hi()
end

function MyTestClassMethods:Bye()
end

local object = MyTestClass.new()
object: -- trigger completion here

• from the following screenshot, you can clearly see that the function is recognized as methods but not fields

If this example still doesn't work on your side, then I really run out of ideas 😇

---

edit2

I hope this screenshot better illustrate my point:

• you need @class on the methods table object
• you should NOT write @field for your methods
• if you write @field for you method, then it will be treated as field instead of method
  see the icons difference between Hi and Bye()

[TracerDS]

Okay, that worked. Thank you very much. The minimal repro did the job as it should. Now I modified it for my purposes and it works as intended ❤