🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
It's time for the first HD Modeling Contest of 2024. Join the theme discussion for Hive's HD Modeling Contest #6! Click here to post your idea!
It's the warning I screenshotted in this post, right?
This warning was introduced with sumneko version 3.7.0, which I hadn't tested until recently. I see that replacing ---@type with ---@class resolves it, but this use of ---@class contradicts my understanding of this annotation and is not documented in sumneko's official documentation either. This makes me unsure, whether it's intended or not.
I'm going to ask this question in sumneko's github.
Until then, I recommend disabling the inject-field diagnostic (see linked post) and continuing to work with ---@type.
The extension is not behaving very smartly for me lately for some reason.
Lua:
if type(self.identifier) == "table" then
for key, __ in pairs(self.identifier) do
self.identifier[key] = nil
end
end
Here I get warnings that I need to check nil or that it cannot assign table | function to table, although I'm checking the type two lines above. It didn't do that before .
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
This warning was introduced with sumneko version 3.7.0, which I hadn't tested until recently. I see that replacing
---@type
with---@class
resolves it, but this use of---@class
contradicts my understanding of this annotation and is not documented in sumneko's official documentation either. This makes me unsure, whether it's intended or not.I'm going to ask this question in sumneko's github.
Until then, I recommend disabling the
inject-field
diagnostic (see linked post) and continuing to work with---@type
.