PowerShell / PowerShell/PSResourceGet
PSResourceInfo tags should not include PSResourceGet impl tags
Open
Nobody has claimed this yet.
Area-Find
Issue-Bug
Up-For-Grabs
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
Steps to reproduce
PSResourceInfo tags should not include PSResourceGet implementation tags only the ones that the user defined and show up on the gallery.
PSScript
PSModule
PSFunction_*
PSCmdlet_*
PSCommand_*
PSEdition_*
PSIncludes_*
etc
Expected behavior
Azure
Deploy
VM
Actual behavior
Azure
Deploy
VM
PSScript
PSFunction_New-RandomString
PSCommand_New-RandomString
PSFunction_Add-VM
PSCommand_Add-VM
PSIncludes_Function
Error details
n/a
Environment data
1.1.0-preview1
Visuals
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the PSResourceInfo tag output described in the issue with PSResourceGet 1.1.0-preview1, comparing gallery-defined tags with implementation tags such as PSScript and PSFunction_*. No source file or test is named; done means PSResourceInfo exposes only the user-defined gallery tags, such as Azure, Deploy, and VM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100