Using Paket for a Grpc project
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
According to Grpc documentation, the package reference for Gprc.Tools should look something like this:
<PackageReference Include="Grpc.Tools" Version="2.23.0">
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
For paket, I found the following issues that seem related: #2370 #4097.
Should it be possible to use the current version of paket with Grpc.Tools, so that the equivalent functionality of the above PackageReference is achieved?
If yes, how can I set this up in paket.dependencies and/or paket.reference?
If no, is it harmful to use paket for all other nuget references, and just add Grpc.Tools as above as PackageReference?
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 reviewing Paket's handling of Grpc.Tools and the related issues #2370 and #4097. Compare the requested PackageReference metadata with what can be expressed in paket.dependencies or paket.reference; done means providing a supported configuration or documenting the limitation and any safe mixed-reference approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100