PowerShell / PowerShell/PSResourceGet
Expose method for generating a .nuspec
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Summary of the new feature / enhancement
The .psd1 file contains all of the info needed to generate a .nuspec, which you're using internally. However, not all nuget hosts are fully compatible with PowerShellGet. Rather than try to target them perfectly, can you not just expose the internals to allow us to build the .nupkg ourselves?
Proposed technical implementation details (optional)
Extract the code for generating .nuspec in https://github.com/PowerShell/PowerShellGet/blob/f41ee9c9583ba26b982008d943a54eb73d4a68da/src/code/PublishPSResource.cs into its own cmdlet.
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 reading src/code/PublishPSResource.cs at the linked revision, focusing on the existing internal code that generates the .nuspec. Extract that generation into a cmdlet, then verify that callers can use the generated .nuspec to build a .nupkg for NuGet hosts outside PowerShellGet.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100