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

GDScript 2.0: Unusual autocomplete "new(" inside member variable #62945

Closed
nathanfranke opened this issue Jul 12, 2022 · 2 comments · Fixed by #94082
Closed

GDScript 2.0: Unusual autocomplete "new(" inside member variable #62945

nathanfranke opened this issue Jul 12, 2022 · 2 comments · Fixed by #94082

Comments

@nathanfranke
Copy link
Contributor

nathanfranke commented Jul 12, 2022

Godot version

v4.0.alpha.custom_build [d26442e]

System information

Arch on 5.18.10-arch1-1

Issue description

weird autocomplete

Steps to reproduce

Type at the top of a script:

var x = ""

And hit enter on the first autocomplete:

image
image

same thing happens with

var x = [""]
var x = $

Minimal reproduction project

No response

@cdemirer
Copy link
Contributor

It's not just arrays:

var x = "
var x = $

@nathanfranke nathanfranke changed the title unusual autocomplete "new(" inside array member variable unusual autocomplete "new(" inside member variable Jul 12, 2022
@Calinou Calinou added this to the 4.0 milestone Jul 12, 2022
@Calinou Calinou changed the title unusual autocomplete "new(" inside member variable GDScript 2.0: Unusual autocomplete "new(" inside member variable Jul 12, 2022
@vnen vnen modified the milestones: 4.0, 4.1 Feb 24, 2023
@YuriSizov YuriSizov modified the milestones: 4.1, 4.2 Jun 22, 2023
adamscott added a commit to adamscott/godot that referenced this issue Aug 25, 2023
- Fixes (partially) godotengine#62945, the issue still exists when you
  autocomplete, then open quotes
@dalexeev dalexeev modified the milestones: 4.2, 4.x Nov 2, 2023
@dalexeev
Copy link
Member

dalexeev commented Nov 2, 2023

The bug is still present in master. Postponed to 4.x because this is a usability issue, not a critical bug and #78288 already in 4.x milestone.

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

Successfully merging a pull request may close this issue.

7 participants