-
-
Notifications
You must be signed in to change notification settings - Fork 336
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
hover is not working as intended #244
Comments
Should be fixed in 1.0.2 |
For performance reasons, I currently do not track the assignment of global variables to a local variable. |
I use lua for a WoW addon i maintain and since require is not supported there is literally no other way to share tables between files besides the namespace table provided by wow lua or using globals i use locals for shorthand access for easy auto-completion and hover for checking if i misstyped something somewhere. |
I am currently sacrificing some accuracy in exchange for performance optimization, but I continue to focus on this matter and explore better solutions that take into account accuracy and performance. I will try some methods tomorrow to restore the search method mentioned in this issue. |
ok version 2.4.8 was working the best way possible but after the 2.4.9 onwards hover is broken again. |
example follows
--a.lua
local t = GlobalTable
t.settings = {
test = 1
}
--b.lua
local b = GlobalTable.settings
print(b.test)
when hovering over settings i can see test = 1
when i type b. i get NO autocomplete and hovering over b says local b: any {}


b shows test:any only because i hard coded it inside print.

Reverting to 0.21.12 for now
The text was updated successfully, but these errors were encountered: