Upgrade packages to minimize the size of dependency graph #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi@246850, I found an issue in the Calamus.TaskScheduler.csproj:
Packages FluentValidation.AspNetCore v9.4.0, FluentValidation.DependencyInjectionExtensions v9.4.0, MySql.Data v8.0.22, NLog.Web.AspNetCore v4.10.0, Quartz v3.2.3, Quartz.AspNetCore v3.2.3, Quartz.Plugins.TimeZoneConverter v3.2.3 and Quartz.Serialization.Json v3.2.3 transitively introduce 108 dependencies into Calamus.TaskScheduler’s dependency graph (see dependency graph before upgrades), while FluentValidation.AspNetCore v9.5.1, FluentValidation.DependencyInjectionExtensions v9.5.2, MySql.Data v8.0.25, NLog.Web.AspNetCore v4.11.0, Quartz v3.3.2, Quartz.AspNetCore v3.3.2, Quartz.Plugins.TimeZoneConverter v3.3.0 and Quartz.Serialization.Json v3.3.1 can only introduce 51 dependencies (see dependency graph after upgrades).
These upgrades can help project minimize the size of dependency graph.
Hope the PR can help you.
Best regards,
sucrose