-
-
Notifications
You must be signed in to change notification settings - Fork 21.5k
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
Autocomplete is inaccurate due to alphabetical sorting of suggestions #21726
Comments
|
Yeah, the linked PR fixes it, but adds some more stuff that made it too big, so it's not merged yet :/ |
Just realized this is not marked as a bug. |
It's working in a less than ideal manner, but it's technically working as intended. Please don't pressure contributors to label everything as a bug 🙂 |
Closing in favor of this proposal: godotengine/godot-proposals#4189 |
Basically this:
I wanted to autocomplete Vector3, but writing Vec3 suggests me PoolVector3Array. This happens when you write letters in different order (in example above I'm skipping "tor"). Autocomplete ignores how you started writing a word and sorts everything alphabetically. I'd expect it to actually select Vector3 in above case.
Another example:
Actually for this one writing "minf" would work, but still, autocomplete could better predict what I'd like to write. I doubt anyone would start RemoteTransform this way.
Tested in 3.1 alpha.
For comparison, here are VS Code results for these completions:
(btw, see how VS Code highlights actual written letters, rather than just the beginning of the suggested words like it is in Godot. But I suppose I could create separate issue for that)
The text was updated successfully, but these errors were encountered: