dotnet-deps-binary-cataloger make the binary scan optional to increase performance/avoid double inclusion
- Dominant language
- Go
- Stars
- 9.6k
- Forks
- 954
- Avg merge
- 23h 27m
- Merged PRs (30d)
- 48
Description
**What would you like to be added**:
Id like there to be an option to avoid cataloging/skipping the dlls in the dotnet-deps-binary-cataloger.
**Why is this needed**:
This will make generation quicker, and avoid existing issues with including dlls.
These range from version mismatches that add a large amount of entries that are useless as they can't be looked up in NuGet and dlls such as Microsoft Azure.Identity Component which has a name mismatch with the actual package Azure.Identity.
Contributor guide
Research direction
Start by locating the dotnet-deps-binary-cataloger and the configuration or command entry point that controls cataloging. Determine how an option to skip DLL cataloging should be exposed, then verify that generation omits those entries when the option is enabled without changing the default behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100