Constraints across package groups?
Open
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Suppose I have two groups Build and Test that depend on the same package Newtonsoft.Json:
source https://nuget.org/api/v2
nuget FSharp.Core
group Build
nuget Newtonsoft.Json
group Test
nuget Newtonsoft.Json
Is there a way to specify that both groups must have the same version of Newtonsoft.Json, without specifying an exact version?
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
The issue names no files, tests, or entry points. Start by locating Paket's handling of dependency groups and version constraints, then determine how groups could share a resolved package version without an exact version requirement. Done means Paket supports and verifies the requested cross-group constraint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100