-
Notifications
You must be signed in to change notification settings - Fork 0
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
export_test.go
pattern yields "Unresolved Reference" messages
#24
Comments
@anpep Thank you for the feedback and helping us reproduce the issue. It looks like we have a package abc, we could import it not only without a package prefix but also via abc. prefix. I was able to reproduce it. Fix will be soon (my best guess is today), most likely in 0.41.1 patch fix, which we will likely release today or tomorrow. |
@anpep Ok. Fixed it. Will release 0.41.1 after a bit of testing, and cleanups. |
Thank you! Will stay tuned |
Ok. The build is out. Please update to 0.41.1 and check whether the problem disappear. |
UPD: The latest release is 0.41.2. One more issue is fixed. |
The problem did disappear. Thank you! |
The problem just reappeared, I don't understand why since I tried yesterday and it worked. Problem exists on both 0.41.2 and 0.41.3 :( |
@anpep Ooops. Do you have the same configuration as described? Or is there anything different? |
Not really, differences are in naming only:
|
@anpep I see a GPL header. Is this code available anywhere on github? |
@anpep BTW, are you sure that it's a tooltitude bug, i.e. is there a tooltitude label in the popup which is shown when you hover over error? UPD: also, could you try exact my example somewhere in your project? Does it reproduce? |
Tooltitude Version: v0.41.0
OS Version:
Linux ubuntu 6.4.16-orbstack-00105-g14094bfeec09 #1 SMP Mon Sep 18 21:45:38 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
VS Code Version: 1.83.1
Go Version:
go version go1.20.10 linux/arm64
Code Repository (if open source):
What did you try to do?
I exported some symbols on a file named
export_test.go
under the package namegrubenv_test
. However, these symbols are not correctly resolved on other files under thegrubenv_test
package.The text was updated successfully, but these errors were encountered: