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

[1.8.4] Conditional IntelliSense failure with #Include #254

Closed
OpalMonkey opened this issue Jan 16, 2023 · 4 comments
Closed

[1.8.4] Conditional IntelliSense failure with #Include #254

OpalMonkey opened this issue Jan 16, 2023 · 4 comments

Comments

@OpalMonkey
Copy link

IncludeTest.ahk

#Requires AutoHotkey v2.0
/**
 * This is a test function.
 * @param {any} p1 - A test parameter.
 * @return {string} Returns a blank string.
**/
TestFunc(p1) {
  
}

Main file:

#Requires AutoHotkey v2.0
#Include IncludeTest.ahk
class TestClass {
  __New(p1) {
    TestFunc()
  }
}
; TestFunc()

If the only calls to TestFunc are within a method or function, the IntelliSense doesn't show up. If the call to TestFunc at the bottom —outside of a block— is uncommented, both locations work correctly. If the definition for TestFunc is in the same file everything works fine.

When I roll back to v1.8.3, this bug doesn't seem to be present.

@thqby
Copy link
Owner

thqby commented Jan 16, 2023

The issue did not reproduce.

@OpalMonkey
Copy link
Author

Hmm, interesting. When I have a chance, I'll test it more carefully to see if it is a conflict with another extension. So far I was able to reproduce it reliably in my setup with the given code while swapping between 1.8.3 and 1.8.4 multiple times.

@OpalMonkey
Copy link
Author

This was bugging me, so I decided to test it now. All other extensions are disabled, using a default theme, and running 1.8.4.

Bug is presenting:
2023-01-16 1-01
With a call to TestFunc not nested in another block, it no longer presents:
2023-01-16 1-02
Include file where TestFunc is defined.
2023-01-16 1-03

I don't know if there is an easy way to temporarily reset all VS Code settings to default or run a clean instance to test if it's a setting, but short of that, I'm not sure how else it could be specific to my setup.

If anyone has any suggestions on how to test it more effectively, I'd be interested to try and find the cause.

@thqby
Copy link
Owner

thqby commented Jan 16, 2023

I see what you mean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants