Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@field to table type no longer resolving values #1046

Closed
lunarwtr opened this issue Apr 12, 2022 · 10 comments
Closed

@field to table type no longer resolving values #1046

lunarwtr opened this issue Apr 12, 2022 · 10 comments
Labels
bug Something isn't working

Comments

@lunarwtr
Copy link

lunarwtr commented Apr 12, 2022

This seemed to break in the last update. Was working ..

---@class Derp
---@field DerpType DerpTypeEnum
Derp = {}

---@class DerpTypeEnum
DerpTypeEnum = {
    Uno = 1,
    Dos = 2,
    Tres = 3
}

Derp.DerpType.  <--- no longer getting assist for table values

image

Now I have to do...
Derp.DerpType = DerpTypeEnum

@sniper00
Copy link

I have same issue

@sumneko sumneko added the bug Something isn't working label Apr 13, 2022
@Rusenec
Copy link

Rusenec commented Apr 13, 2022

Yes, same issue here. Suddenly hundreds of warning for not resolving and undefined values.

@sumneko
Copy link
Collaborator

sumneko commented Apr 14, 2022

Should be fixed

@sumneko sumneko closed this as completed Apr 14, 2022
@lunarwtr
Copy link
Author

image

@lunarwtr
Copy link
Author

can't wait to try it.. ty sumneko

@sumneko
Copy link
Collaborator

sumneko commented Apr 14, 2022

can't wait to try it.. ty sumneko

At present, there are only some performance problems left. If they cannot be solved quickly, I will publish a fixed version tomorrow then look into the performance problems.

@Rusenec
Copy link

Rusenec commented Apr 15, 2022

Is this a fix for the problem with "undefined fields"? I still get hundreds of those with the 3.0.1 version?

@sumneko
Copy link
Collaborator

sumneko commented Apr 15, 2022

Is this a fix for the problem with "undefined fields"? I still get hundreds of those with the 3.0.1 version?

You can manually update server from CI: https://github.com/sumneko/lua-language-server/actions/runs/2169530054
Or you can wait 3.0.2, should be published today.

@Rusenec
Copy link

Rusenec commented Apr 15, 2022

Is this a fix for the problem with "undefined fields"? I still get hundreds of those with the 3.0.1 version?

You can manually update server from CI: https://github.com/sumneko/lua-language-server/actions/runs/2169530054 Or you can wait 3.0.2, should be published today.

Hey sumneko, I installed 3.0.2 and still getting the same problems. Only returning to 2.6.8 fixes it. Any ideas what I could do?

@sumneko
Copy link
Collaborator

sumneko commented Apr 15, 2022

Is this a fix for the problem with "undefined fields"? I still get hundreds of those with the 3.0.1 version?

You can manually update server from CI: https://github.com/sumneko/lua-language-server/actions/runs/2169530054 Or you can wait 3.0.2, should be published today.

Hey sumneko, I installed 3.0.2 and still getting the same problems. Only returning to 2.6.8 fixes it. Any ideas what I could do?

Please open a new issue and provide your example code.

EDIT: Please check #980 first

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants