-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[Commands] Migrate: Group manifest update errors per target #8677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[Commands] Migrate: Group manifest update errors per target #8677
Conversation
If migrate fails to insert one or more features into the manifest for a target, let's produce a single error that lists all of the features, this makes the logging less noisy.
@swift-ci please test |
@swift-ci please test self hosted Linux |
@swift-ci please test self hosted |
@swift-ci please test macOS platform |
@swift-ci please test Windows platform |
@swift-ci please test |
@swift-ci please test Windows platform |
@swift-ci please test self hosted Windows platform |
6 similar comments
@swift-ci please test self hosted Windows platform |
@swift-ci please test self hosted Windows platform |
@swift-ci please test self hosted Windows platform |
@swift-ci please test self hosted Windows platform |
@swift-ci please test self hosted Windows platform |
@swift-ci please test self hosted Windows platform |
Motivation:
If migrate fails to insert one or more features into the manifest for a target, let's produce a single error that lists all of the features, this makes the logging less noisy.
Modifications:
SwiftPackageCommand
to request manifest to all of the features related to a target and produce a single error if that fails.Result:
If manifest has some non-standard ways of defining targets or settings that cannot be updated by
AddSettting
, migration logging is going to be more organized and less noisy.