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 has been archived by the owner on Jul 15, 2023. It is now read-only.
fmt. gives completions for all the symbols from the fmt package template. doesn't do the same.
This is because we cannot determine which of the text/template and html/template should be used.
Proposed fix:
When encountering template. provide completions for all the matching pkgs
Once user chooses the package, the import should be added for that package, and completions should be triggered again.
This is possible to do because we can run commands as part of the completion. But since we can run one 1 command for a completion item, we will have to create a new command that internally runs go.import.add command followed by triggering suggestions again with editor.action.suggest command
The text was updated successfully, but these errors were encountered:
I was able show all the matching packages in case of template, was wondering how should I proceed to forward if the user selects one of the packages to add it in import path and provide subsequent completions.
For multiple matching packages I included the token and the matching packages in parenthesis, in this case would adding command which imports the package be the right thing to do?
fmt.
gives completions for all the symbols from the fmt packagetemplate.
doesn't do the same.This is because we cannot determine which of the
text/template
andhtml/template
should be used.Proposed fix:
template.
provide completions for all the matching pkgsThis is possible to do because we can run commands as part of the completion. But since we can run one 1 command for a completion item, we will have to create a new command that internally runs
go.import.add
command followed by triggering suggestions again witheditor.action.suggest
commandThe text was updated successfully, but these errors were encountered: