-
Notifications
You must be signed in to change notification settings - Fork 298
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
Tab completion for command parameters shows invalid candidates #1
Comments
Oh, I see that the latter - failing case - has an [AllowNullAttribute] - could that be it? |
This is a general PowerShell issue. As odd as it sounds, it looks like it depends whether or not there are multiple parameters with a common prefix. If there is a common prefix for more than 1 parameter, PowerShell will never suggest an already specified parameter. If the parameter has a unique prefix, PowerShell will suggest that parameter even if it has been specified. Try this: function foo($qqq, $zzz1, $zzz2) {}
foo -qqq 1 -q<TAB> # will suggest -qqq
foo -zzz1 1 -z<TAB> # will only suggest -zzz2
foo -zzz1 1 -zzz2 2 -z<TAB> # will suggest neither -zzz1 nor -zzz2 |
But it's a bug, right? I think you might know the guy who wrote the tab completion stuff, no? :) |
I asked the author of that code (no, it wasn't me) and he said it was by design, but I convinced him it was a bad design so he now considers it a bug. Maybe open a bug on Connect? |
Ok, I'll just log it as it stands - I thought you were trying to justify -Oisin On Wed, May 15, 2013 at 2:10 PM, Jason Shirk [email protected]:
404 signature missing |
I can't see immediately why this happens, but here's a repro:
A cursory look at parameter metadata yield no clues, sorry!
The text was updated successfully, but these errors were encountered: