Activity

1. xtqqczze

   added

   Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bug

   on Jan 27, 2019
2. xtqqczze commented on Jan 27, 2019

   

   xtqqczze

   on Jan 27, 2019

   Last edited by xtqqczze

   ContributorAuthor

   More actions

   Parameters should be named in common with Get-Command.

   Get-Command [[-Name] <string[]>] [[-ArgumentList] <Object[]>] [-Module <string[]>] [-FullyQualifiedModule <ModuleSpecification[]>] [-CommandType <CommandTypes>] [-TotalCount <int>] [-Syntax] [-ShowCommandInfo] [-All] [-ListImported] [-ParameterName <string[]>] [-ParameterType <PSTypeName[]>] [<CommonParameters>]
   
3. iSazonov commented on Jan 28, 2019

   

   Ilya (iSazonov)

   on Jan 28, 2019

   Collaborator

   More actions

   I think it's not worth the effort. You can always use Get-Command cmdlet for these purposes.
4. xtqqczze commented on Jan 28, 2019

   

   xtqqczze

   on Jan 28, 2019

   ContributorAuthor

   More actions

   Ilya (@iSazonov) A common pattern is to use the Get-Command cmdlet with the ErrorAction parameter set to SilentlyContinue, although this hides all errors:

   [bool](Get-Command -Name git -CommandType Application -ErrorAction SilentlyContinue)

   Alternatively, the specific exception can be caught:

   try {
       [bool](Get-Command -Name git -CommandType Application -ErrorAction Stop)
   }
   catch [System.Management.Automation.CommandNotFoundException] {
       $false
   }
5. iSazonov commented on Feb 2, 2019

   

   Ilya (iSazonov)

   on Feb 2, 2019

   Collaborator

   More actions

   Steve Lee (@SteveL-MSFT) My suggestion is to close as Won't-Fix - what is your conclusion?
6. SteveL-MSFT commented on Feb 6, 2019

   

   Steve Lee (SteveL-MSFT)

   on Feb 6, 2019

   Member

   More actions

   Ilya (@iSazonov) well, if you look at the original linked issue #7562, I opened it :)

   The discussion in the @PowerShell/powershell-committee on a different topic acknowledged that PowerShell should have had more Test-* cmdlets rather than having scripts rely on Get-* with error handling and checking against $null. Also, with more Test-* cmdlets, it would make it feasible to use cmdlets directly as DSC resources (Get/Set/Test). It's unlikely the PowerShell team would spend the time implementing this. However, this specific cmdlet should be relatively easy and straightforward and would encourage the community to pick it up.
7. iSazonov commented on Feb 6, 2019

   

   Ilya (iSazonov)

   on Feb 6, 2019

   Collaborator

   More actions

   Steve Lee (@SteveL-MSFT) Thanks for remainder! So the issue is a duplicate and we can track in #7562.
8. JamesWTruher commented on Jun 1, 2021

   

   James Truher (JamesWTruher)

   on Jun 1, 2021

   Collaborator

   More actions

   duplicate of #7562, this is a great discussion with some good detail. We'll refer to it from #7562 when it's time for implementation.
9. James Truher (JamesWTruher)

   closed this as completedon Jun 1, 2021