Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider completing arguments to sub commands when using dotnet 1.x CLI #4

Open
lzybkr opened this issue Nov 26, 2017 · 1 comment
Open

Comments

@lzybkr
Copy link

lzybkr commented Nov 26, 2017

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>
@bergmeister 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
@bergmeister
Copy link
Owner

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants