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
{{ message }}
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Also happens when you do something like -. or *., all of which is a little goofy. This is probably happening because it's not finding any nodes when looking up the location in the AST and therefore treated like completion on an empty line or similar.
This is VS Code feature. We do not trigger anything, VS Code does. We could look into the trigger character theoretically, but, IMO, this is just a cosmetic issue.
I understand that VSC is what's sending the request for completion, but I'd be curious to know why we actually return something, rather than to, say, look behind the ., find nothing, so return nothing. (Not to mention how interesting it is that everything that is suggested is some derivative of Exception.)
Also happens when you do something like
-.
or*.
, all of which is a little goofy. This is probably happening because it's not finding any nodes when looking up the location in the AST and therefore treated like completion on an empty line or similar.Found in #334.
The text was updated successfully, but these errors were encountered: