Re: Get-ChildItem Needs a Type parameter
- From: "Keith Hill" <r_keith_hill@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 1 Dec 2005 16:24:15 -0700
"James Truher [MSFT]" <jimtru@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23Iab6Ss9FHA.1440@xxxxxxxxxxxxxxxxxxxxxxx
>I usually wind up filtering with where:
>
> gci . -rec | where { ! $_.MshIsContainer } | ...
>
> An issue that I see with providing a "type" parameter for the core
> cmdlets, is that not all providers will necessarily have a leaf/container
> (think variable/function drive). However, dynamic parameters reflects the
> functionality of the underlying resource - perhaps this could be done in
> that way - I'm not sure whether this has been filed as a feature request -
> please do so
Yeah I filed an enhancement request a few days ago - 219377051. I need to
try using the -filter option. I haven't yet. I could see where it might
make sense to do this with a filter. However since filter is just a
"string", the discoverability suffers as well as potential intellisense
support in the future. Hmm.
--
Keith
.
- References:
- MSH: Get-ChildItem Needs a Type parameter
- From: Keith Hill
- Re: Get-ChildItem Needs a Type parameter
- From: James Truher [MSFT]
- MSH: Get-ChildItem Needs a Type parameter
- Prev by Date: Re: SWbemLocator: Access is denied.
- Next by Date: Re: [MSH] sorting / enumerating of a HashTable
- Previous by thread: Re: Get-ChildItem Needs a Type parameter
- Next by thread: Re: All Users and their Security Groups
- Index(es):
Relevant Pages
|
