Nuget packages version ranges
- Dominant language
- C#
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
When downloading nuget packages version ranges should be taken in consideration.
- Add infrastructure to download the api/v2/Packages()/... query results
- Verify the correctness of the xml
- Resolve the dependencies according to the entry dependencies node
- Download the dependencies
- Download the package according to the versioning (if needed)
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating the existing package-download path, then inspect how NuGet api/v2/Packages() query results and XML dependencies would fit into it. Done means version ranges are resolved, dependencies are downloaded, and the requested package is downloaded for the selected version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100