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
After typing . or when hitting Ctrl + Space, VSCode shows a list of members of the struct, including functions. This list, currently, also displays some members of members, and there is no way to disable this behavior:
Please consider adding an option to disable this behavior.
The text was updated successfully, but these errors were encountered:
This actually happens to already exists, in the form of an internal (hidden) option: "deepCompletion": false.
Currently, that exists only for tests--we don't advertise it or expect our users to use it.
Can you say more about why you don't want this behavior? For example, if you were completing in the context where a uint type is expected, deep completion can find completions (address.number) that match the implied type constraint.
IIRC we limit the number of deep completions (I think to 3).
Can you say more about why you don't want this behavior? For example, if you were completing in the context where a uint type is expected, deep completion can find completions (address.number) that match the implied type constraint.
I'm the author of Windigo, which is under heavy refactoring right now. That's where I noticed some odd stuff showing.
While in some cases the deep completion is indeed useful (like in the Address example), in some cases it shows misleading or nonsensical choices, like:
Maybe in addition of true and false, we could have an option to deep complete just structs, not results from functions.
Even so, I believe disabling deep completion would lead to less visual pollution – and since it's a matter of preference, I believe it would do no harm. It would be opt-out anyway.
After typing
.
or when hitting Ctrl + Space, VSCode shows a list of members of the struct, including functions. This list, currently, also displays some members of members, and there is no way to disable this behavior:Please consider adding an option to disable this behavior.
The text was updated successfully, but these errors were encountered: