-
Notifications
You must be signed in to change notification settings - Fork 20
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
Incorrect W0017 warning #23
Comments
I am unable to reproduce the warning. I tried pasting your code into an existing valid erlang project, into an empty directory, and creating a test for it. None of these showed the problem. And I will update the docs, thanks. Please provide more specific instructions to re-create the error. |
Hmm... It doesn't always work for me either. I have created this file as However, if I close the file in VS Code and then open the file again, I don't get the error any more. Closing VS Code and typing Quite confusing, to be honest. |
Summary: Address #23 - Fix reported documentation error - Add test to confirm the normal operation for the provided repro case Reviewed By: robertoaloi Differential Revision: D56413056 fbshipit-source-id: eaaea7279c5661135ce03d7444535c4088ef58b0
I tested it by making I am not prepared to give VS Code trust access to my entire home directory. |
I don't think the directory would matter. I was initially suspecting that a space in the path could have been relevant, but it isn't. I think what's important is that |
And I am looking into why we cant set the log level, and why our config settings show up a "Example configuration". |
For me But I see this in the Extension Host output (when log level is set to trace):
|
You need to select And I have a new release coming that lets you set logging in more detail |
@dszoboszlay I cannot reproduce this either. Did you manage to get the logging working, so we can have a look at what's happening for you? |
I was too fast. I can indeed reproduce this. Here are the steps.
Reason:
|
Describe the bug
A fully qualified function call to the current module incorrectly triggers a W0017 (function is undefined) warning.
Furthermore, the doc page of the warning has an incorrect title. It says Unused Function while it should be Undefined Function.
To Reproduce**
Type this into VS Code:
Expected behavior
There shouldn't be any warnings reported in this module.
Actual behavior
The last line is marked with W0017.
Context
elp version
):elp 1.1.0+build-2024-04-17
v0.21.0
extensionThe text was updated successfully, but these errors were encountered: