Respect contentfiles nodes if present in nuget packages
Open
Nobody has claimed this yet.
enhancement
nupkg spec
up-for-grabs
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Per https://docs.nuget.org/create/nuspec-reference#contentfiles-with-visual-studio-2015-update-1-and-later, there is a new 'contentFiles' node in the nupkg that is used to signal language-dependent, immutable content files in a known order. We should support this.
Contributor guide
No contributing guide indexed for this repository
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
No source files or tests are named in the issue. Start by reading the linked NuGet nuspec reference for the contentFiles node, then trace Paket's NuGet package content-handling entry points. Done means packages containing contentFiles are recognized and handled according to that specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100