API for adding binaries from packages when packing
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
When packing analyzers I think the idea is that binaries from nuget dependencies are supposed to go into the analyzer package.
It can be solved via:
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
And:
bin/Release/Gu.Roslyn.AnalyzerExtensions.dll ==> analyzers/dotnet/cs
Probably not worth it to add paket.template API for this but asking any way. Maybe something like:
included_files:
Gu.Roslyn.AnalyzerExtensions.dll ==> analyzers/dotnet/cs
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
Start by examining Paket's paket.template handling and the packing flow for analyzer packages. Check how CopyLocalLockFileAssemblies and the bin/Release/Gu.Roslyn.AnalyzerExtensions.dll to analyzers/dotnet/cs mapping could be represented, then determine what tests would verify an included_files API and its resulting package contents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100