You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The core issue I'm having is that I find that as my projects grow larger and scripts/classes more complex the autocomplete functionality becomes slower to use since it will offer such a lot of options that it takes more time to pick the one I'm after. And often in these situations I can see that most of the options offered are incompatible with the current context I'm typing code in.
A somewhat extreme example:
In this case as I'm writing the second parameter in a for statement context I'm thinking that the editor should be aware that this should likely be an Array. And in this situation it would be very useful if it could sort suggested completions that return arrays at the top. In this example case selectionManager.selectedLayers that is an array (and what I'm looking for). While for example the similarly named signals and functions (that return bool, or have no return value at all) are less likely to be what I'd like to enter in this context.
This example is from a for statement, but the situation is the same when entering typed function parameters or assigning values to typed variable, when auto-completion could know what type is expected in this context and could then recommend completions that are of an expected type.
Since the type returned from functions and type of variables is known (if they're typed) this part of the information should already be available to the auto-complete system. What I don't know is if the current code typing context expected type is know to the system, or how complicated this would be to figure out. There is some hint of it when writing function calls, since it can show you what the next expected variables are:
And even if auto-complete can't figure out the expected/recommended type in a lot of cases just having it offer recommendations in some simple common cases like typed function parameters would I think be a great improvement.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The core issue I'm having is that I find that as my projects grow larger and scripts/classes more complex the autocomplete functionality becomes slower to use since it will offer such a lot of options that it takes more time to pick the one I'm after. And often in these situations I can see that most of the options offered are incompatible with the current context I'm typing code in.
A somewhat extreme example:

In this case as I'm writing the second parameter in a
for
statement context I'm thinking that the editor should be aware that this should likely be an Array. And in this situation it would be very useful if it could sort suggested completions that return arrays at the top. In this example caseselectionManager.selectedLayers
that is an array (and what I'm looking for). While for example the similarly named signals and functions (that return bool, or have no return value at all) are less likely to be what I'd like to enter in this context.This example is from a
for
statement, but the situation is the same when entering typed function parameters or assigning values to typed variable, when auto-completion could know what type is expected in this context and could then recommend completions that are of an expected type.Since the type returned from functions and type of variables is known (if they're typed) this part of the information should already be available to the auto-complete system. What I don't know is if the current code typing context expected type is know to the system, or how complicated this would be to figure out. There is some hint of it when writing function calls, since it can show you what the next expected variables are:
And even if auto-complete can't figure out the expected/recommended type in a lot of cases just having it offer recommendations in some simple common cases like typed function parameters would I think be a great improvement.
Beta Was this translation helpful? Give feedback.
All reactions