Error "Undefined field" on _G if global is declared by Lua.diagnostics.globals

[myocytebd]

How are you using the lua-language-server?

Visual Studio Code Extension (sumneko.lua)

Which OS are you using?

Linux

What is the issue affecting?

Diagnostics/Syntax Checking

Expected Behaviour

local extract0 = bit32 and bit32.extract -- Lua 5.2/Lua 5.3 in compatibility mode
local extract = _G.bit32 and _G.bit32.extract -- Lua 5.2/Lua 5.3 in compatibility mode

Expected: No error

Actual Behaviour

Error on 2nd line:

(global) _G.bit32: unknown
Undefined field bit32.Lua Diagnostics.(undefined-field)

Reproduction steps

1. Add 'bit32' to globals;
2. Errors on 1st line disappeared; but errors on 2nd line persists.

Additional Notes

sumneko.lua-3.6.18-linux-x64

Real global variables does not trigger errors. Only Lua.diagnostics.globals items lead to errors.

Additional question: how to mute errors for this pattern?

if _G.bit then -- LuaJIT
    local shl, shr, band = _G.bit.lshift, _G.bit.rshift, _G.bit.band
...
end

@diagnostic disable: mute too much, but @diagnostic disable-line: mute too little.

Log File

No response

[NyaMisty]

Very sad that it's one and half year pasted and this issue still persists without any workaround :(

[tomlau10]

In the use case above, I think what you want is enabling those built-in library no matter what runtime version?

• .luarc.json

    "runtime.builtin": {
        "bit32": "enable",
        "bit", "enable",
    },

• But this will turn the warning into Deprecated.(Defined in Lua 5.2, current is Lua 5.4.) 🤔
  At least disabling the deprecated will not be too much as disabling undefined-field

---@diagnostic disable: deprecated

local extract0 = bit32 and bit32.extract -- Lua 5.2/Lua 5.3 in compatibility mode
local extract = _G.bit32 and _G.bit32.extract -- Lua 5.2/Lua 5.3 in compatibility mode

if _G.bit then -- LuaJIT
    local shl, shr, band = _G.bit.lshift, _G.bit.rshift, _G.bit.band
...
end

-- no more warnings :)

• you may also disable deprecated diagnostic globally in the workspace

    "diagnostics.neededFileStatus": {
        "deprecated": "None!"
    },

or turn its severity to Hint level only (such that no warning msg will be shown, only a strikethrough effect)

    "diagnostics.severity": {
        "deprecated": "Hint"
    },

---

Note that this does not fix the actual issue described in the title.
This just solve the use case that the global variable in question is a built-in library.