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
It would be nice for completion to be smarter about the context.
For example, if I type:
dotnet new <TAB>
As currently implemented, when I hit TAB< I get commands like new again even though it doesn't make sense.
Completion should only suggest valid arguments to the new sub-command or valid templates for a new project.
To see one way to do this, see here - this code supports completing service names in the following context:
net start <TAB>
The text was updated successfully, but these errors were encountered:
bergmeister
changed the title
Consider completing arguments to sub commands
Consider completing arguments to sub commands when using dotnet 1.x CLI
Nov 26, 2017
@lzybkr I have modified the title now to reflect that the new version posh-dotnet uses now the dotnet CLI API for version 2 of the dotnet CLI. Therefore this issue applies now only to version 1.x of the dotnet cli.
It would be nice for completion to be smarter about the context.
For example, if I type:
As currently implemented, when I hit TAB< I get commands like
new
again even though it doesn't make sense.Completion should only suggest valid arguments to the
new
sub-command or valid templates for a new project.To see one way to do this, see here - this code supports completing service names in the following context:
The text was updated successfully, but these errors were encountered: