[dotnet] Support for Central Package Management
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
Describe the bug
I am raising this as a bug as I think it was missed as is quite important.
here we are trying to fix PRs. However, all the dependency version live in Packages.Props or Directory.Packages.Props seE: https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management
Current behavior
It fails trying to issue a fix thats a direct dependency.
Reproduction steps
No response
Expected behavior
No response
JFrog Frogbot version
2.19.9
Package manager info
nuget
Git provider
GitHub
JFrog Frogbot configuration yaml file
No response
Operating system type and version
Linux
JFrog Xray version
3.74.8
Contributor guide
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 in packagehandlers/nugetpackagehandler.go around line 18 and compare its dependency-fix behavior with NuGet Central Package Management, especially Packages.Props and Directory.Packages.Props. Done means Frogbot can issue fixes for dependencies whose versions are managed in those central files; the issue provides no reproduction or test file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100