Union table|class doesn't accept a generic table and only accepts a class instance (causing false missing-fields diagnostic) about lua-language-server HOT 3 OPEN

Just make the class fields optional

---@class TestClass
---@field TestField number? A test field in test class
TestClass = {}

from lua-language-server.

Just make the class fields optional

Thanks for the suggestion! That was the first workaround I tried, but it gives off the wrong impression as real instances of the class always have the fields. It also makes it possible to pass a generic table to a function that only accepts the class.

So for a workaround for now I did this:

---Define a custom class for generic tables (workaround for LLS bug https://github.com/LuaLS/lua-language-server/issues/2606)
---@class any_table
any_table = {}

---@class TestClass
---@field TestField number A test field in test class
TestClass = {}

-- TestFunction1
---@param generic_table_or_testclass_instance any_table|TestClass
function TestFunction1(generic_table_or_testclass_instance) end

With this LLS is smart enough to allow both while keeping the strictness on functions that only accept a class. For functions that only accept a table I keep using the regular table, I only use any_table for overloaded function.

But I still think LLS should be fixed to make it work without the fake table class :-)

from lua-language-server.

Yes, it is a shame that there are too many specific use cases, I have also come across some things that I would like to do and it is not possible, I just accept it and hope that in the future,
After the famous Rework that they will do to LLS we should be able to cover all the problems and even be able to create solutions in itself with dynamic annotations or that execute lua code

from lua-language-server.