You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my workspace, I use a custom script that runs when I start VSCode and (re-)generates a bunch of LUA Meta files that contain an API I use. However, because this happens at the same time as the lua language server analyzes the workspace the two processes conflict somehow, leading to the language server not properly analyzing these files, and listing a lot of "undefined global" problems as a result. Even if the langauge server later re-analyzes the workspace as I'm working, these problems do not go away. Regenerating the files again later also does not fix the issue.
I expect the language server to re-analyze the files after they are generated to properly compile the list of globals etc, alternatively I think my problem could also be solved by adding a command that I can call to force the language server to reanalyze the entire workspace, which I could call after the files are generated, or a config value to delay the inital analysis of the workspace by a few seconds.
Actual Behaviour
The language server does not find the generated Meta files and instead lists a lot of "undefined global" issues that don't go away.
This is not consistent, when restarting VSCode it only happens around 50% of the time.
Reproduction steps
Start VSCode with the workspace
Wait for the Meta files to be generated
Wait for the LUA langauge server to finish analyzing
Notice a large number of issues raised in the Problem panel
Additional Notes
This is on version 3.5.5 btw, because 3.5.6 frequently breaks the code colour formatting.
Log File
No response
The text was updated successfully, but these errors were encountered:
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?
Diagnostics/Syntax Checking
Expected Behaviour
In my workspace, I use a custom script that runs when I start VSCode and (re-)generates a bunch of LUA Meta files that contain an API I use. However, because this happens at the same time as the lua language server analyzes the workspace the two processes conflict somehow, leading to the language server not properly analyzing these files, and listing a lot of "undefined global" problems as a result. Even if the langauge server later re-analyzes the workspace as I'm working, these problems do not go away. Regenerating the files again later also does not fix the issue.
I expect the language server to re-analyze the files after they are generated to properly compile the list of globals etc, alternatively I think my problem could also be solved by adding a command that I can call to force the language server to reanalyze the entire workspace, which I could call after the files are generated, or a config value to delay the inital analysis of the workspace by a few seconds.
Actual Behaviour
The language server does not find the generated Meta files and instead lists a lot of "undefined global" issues that don't go away.
This is not consistent, when restarting VSCode it only happens around 50% of the time.
Reproduction steps
Additional Notes
This is on version 3.5.5 btw, because 3.5.6 frequently breaks the code colour formatting.
Log File
No response
The text was updated successfully, but these errors were encountered: