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

Error "Unexpected Identfier in class body" shows wrong line #96792

Closed
tobydjones opened this issue Sep 10, 2024 · 1 comment · Fixed by #99887
Closed

Error "Unexpected Identfier in class body" shows wrong line #96792

tobydjones opened this issue Sep 10, 2024 · 1 comment · Fixed by #99887

Comments

@tobydjones
Copy link

Tested versions

4.3

System information

Godot v4.3.stable - Windows 10.0.19045 - GLES3 (Compatibility) - AMD Radeon RX 6600 (Advanced Micro Devices, Inc.; 31.0.24033.1003) - Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (8 Threads)

Issue description

The parser error Error at (3,16): Unexpected "Identifier" in class body. is reporting the wrong line

Steps to reproduce

Make a new script with the following lines

extends Node2D

var test = true
error = true

The error message will say the error is on line 3, at the end of the line, and that line will be highlighted, but the error is on line 4

Minimal reproduction project (MRP)

N/A

@dalexeev
Copy link
Member

@github-project-automation github-project-automation bot moved this to For team assessment in GDScript Issue Triage Sep 10, 2024
@dalexeev dalexeev moved this from For team assessment to Up for grabs in GDScript Issue Triage Sep 10, 2024
@dalexeev dalexeev moved this from Up for grabs to Fix pending review in GDScript Issue Triage Dec 6, 2024
@dalexeev dalexeev added this to the 4.4 milestone Dec 6, 2024
@github-project-automation github-project-automation bot moved this from Fix pending review to Done in GDScript Issue Triage Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants