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

TabExpansion++ should use OutputType filter command completion in a pipeline #10

Open
lzybkr opened this issue Apr 22, 2013 · 1 comment

Comments

@lzybkr
Copy link
Owner

lzybkr commented Apr 22, 2013

Many built-in commands specify OutputType. Command completion could leverage this by only returning commands that take an object of type OutputType as a pipeline parameter. For example:

Get-Disk |

Here we could suggest only commands that accept a MSFT_Disk, e.g. these commands:

Get-Command -ParameterType MSFT_Disk

@bielawb
Copy link
Contributor

bielawb commented Apr 22, 2013

I like this idea but I guess we would need to include all cmdlets that support binding ByPropertyName for any of their parameters too... Even if none of the properties match the parameter there is still scriptblock that user could pass to convert property to parameter: One I use from time to time (with some filters to it) is Get-Process | Get-ChildItem.

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

No branches or pull requests

2 participants