Meta Issue: can't explicitly search for a cmdlet name in an issue
See original GitHub issueSummary of the new feature / enhancement
Because of #3080
Searching difficulties with hyphens (-) and periods (.) and due to the fact that PowerShell uses a verb-noun pair for the names of cmdlets, it is quite difficult to narrow an issue search to a meaningful cmdlet name, e.g.:
Write-Output in:title
Results in 8+25=33 issues where only 19 issues actually have Write-Output
in the title.
(not even mentioning here to do a wide general search on all comments in an issue)
Proposed technical implementation details (optional)
Not sure whether I missed some documentation or workaround for this…
Anyways, creating labels for each known cmdlet (as Add-Member
, Write-Host
, …) and automatically add that cmdlet label when recognized in a comment might help here.
Issue Analytics
- State:
- Created 3 months ago
- Reactions:3
- Comments:10 (1 by maintainers)
Top Results From Across the Web
can't explicitly search for a cmdlet name in an issue
Meta Issue : can't explicitly search for a cmdlet name in an issue #19191. Sign in to view logs · Sign in to...
Read more >PowerShell: Cmdlet Connect-MicrosoftTeams not found ...
I can see the output shows you have installed the module successfully. However, it seems to have some problem. I suggest you re-install...
Read more >Resolving PowerShell module assembly dependency ...
This presents issues when a module's dependencies conflict with already-loaded DLLs and may prevent using two otherwise unrelated modules in the ...
Read more >Importing a PowerShell Module
PowerShell 2.0 uses the appropriately-named Import-Module cmdlet to import modules. When this cmdlet is run, Windows PowerShell searches for ...
Read more >MSOnline Module - Installation and Troubleshooting
How to install the MSOnline module and fix the most common errors. If installation of MSOnline fails follow the steps in this guide...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@iRon7 I have moved this to Needs Investigation as I am hoping this is something that is globally off but can be turned on at org/repo level and have reached out asking about this. Will report back if/when I hear or find out from my investigations any further on this as it really is a big pain point for us in this repo and other PowerShell related repos too.
IMHO the main reason for not doing this is having 300 tags would be very awkward to work with - the present number is already too many. If a bot could see some terms in titles and add those as tags that would save work. (I’m not sure if normal users would be able to add the tag and relying on authorized ones to do the little bits of work seems a bad idea).
"Write-Output"
finds that text but thein:title
tag seems to process as (write in:title) and (output in:title) It’s really an issue on github’s side and should be reported there because it will help other repos.However if no fix is forthcoming from there we should see if there is some way we can make it easier - users checking if they are duplicating an issue don’t always find the duplicate because of limitations of search, commenting to existing issues rather than creating extra ones would help everyone.