Removed assemblies should be remembered
- Dominant language
- C#
- Stars
- 126
- Forks
- 39
- Avg merge
- 17h 36m
- Merged PRs (30d)
- 1
Description
Upgrade Planner allows removing assemblies. We currently completely remove them and forget that we ever had them. Very often these are 3rd party components which we don't want to analyze and know they are support (for example, xUnit or other well-known NuGet packages).
This causes noise as we also report missing dependencies and the removed assemblies are now showing up as unresolved.
Instead, we should remember the removed assemblies and excluded them from missing dependencies. This still catches inadvertent exclusions while not causing noise for intentional removals.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the Upgrade Planner removes assemblies and how it reports missing dependencies. Make removed assemblies persist as exclusions and ensure they are omitted from missing-dependency results while other inadvertent exclusions remain detectable; verify the behavior with the project's existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100