LuaLS / LuaLS/lua-language-server

Nested property type lost when accessed from reference

Open
#1,613 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

as designed
Dominant language
Lua
Stars
4.4k
Forks
442
PR merge metrics
No merged PRs in 30d

Description

### How are you using the lua-language-server?

Visual Studio Code Extension (sumneko.lua)

### Which OS are you using?

Windows

### What is the issue affecting?

Type Checking

### Expected Behaviour

``` ---@class A
local A = {}

---@class B
---@overload fun(): B
local B = {}

---@class C
---@overload fun(): C
local C = {}

A.property1 = B()

A.property1.property2 = C()

local refToB = A.property1

local refToC = refToB.property2
```

while the local `refToB` is correctly of type `B`, it no longer is aware of property2.

![image](https://user-images.githubusercontent.com/9368775/194184793-8e81f1bf-5a1f-4355-9878-8871c6740501.png)

expected behavior would be that it is aware of the properties assigned to the instance.

### Actual Behaviour

presence of property is lost in the "instance" of object B (not definition).

### Reproduction steps

1. Go to '...'
2. Click '...'
3. See error '...'

### Additional Notes

_No response_

### Log File

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Lua type-checking example in the issue and reproduce the missing property information through the assignments to A.property1, refToB, and refToC. Trace the relevant type-checking behavior until refToB retains property2 and refToC resolves as C; no repository file or test is named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.