LuaLS / LuaLS/lua-language-server
There is no missing-field diagnostic for 'number' fields
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 4.4k
- Forks
- 442
- PR merge metrics
- No merged PRs in 30d
Description
(Split from: https://github.com/LuaLS/lua-language-server/issues/2279)
I would expect the following code to error with a missing-field for [0]
```
---@class TestClass
---@field [0] string
---@field test string
---@param test TestClass
local function test(test)
end
test({test = "test"})
```
but none is given.
Note: there is type checking on the field
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported Lua snippet in the language server and compare the missing-field behavior for the numeric field [0] with the existing type-checking behavior. Trace the missing-field diagnostic path and its handling of numeric keys; done means the example reports [0] as missing while preserving the existing field type check.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100