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

Unable to recognize the newly created class name. #787

Open
jesspig opened this issue Jan 31, 2025 · 2 comments
Open

Unable to recognize the newly created class name. #787

jesspig opened this issue Jan 31, 2025 · 2 comments
Labels
bug language server Issue is not originating from this extension, but from the LSP instead

Comments

@jesspig
Copy link

jesspig commented Jan 31, 2025

Godot version

v4.4.beta (4ce466d7f)

VS Code version

1.96.4

Godot Tools VS Code extension version

2.3.0

System information

Windows 11

Issue description

If you don't restart LSP after defining the class name A1 with class_name, B2.gd will prompt Could not find type in the current scope. This doesn't affect running in the Godot editor, but it will display a red wavy line in VSCode.

Steps to reproduce

A1.gd

class_name A1

# other code
...

B2.gd

...
# other code

var a1: A1 = A1.new()

# other code
...
@jesspig jesspig added the bug label Jan 31, 2025
@JohnC0de
Copy link

JohnC0de commented Feb 7, 2025

Bump, same happens with Autoload/Globals

@DaelonSuzuka DaelonSuzuka added the language server Issue is not originating from this extension, but from the LSP instead label Feb 7, 2025
@DaelonSuzuka
Copy link
Collaborator

Please use the search function. This a very old, very known issue with the language server not properly refreshing itself. This extension has nothing to do with it and it cannot be fixed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug language server Issue is not originating from this extension, but from the LSP instead
Projects
None yet
Development

No branches or pull requests

3 participants