-
Notifications
You must be signed in to change notification settings - Fork 216
Implement additional argument validation steps and record multiple failures before exiting #243
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
Conversation
|
@swift-ci test |
DougGregor
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! Thank you
|
Looks like I made a small mistake with the original implementation - a couple of these diagnostics should be warnings. Thanks for the quick review @DougGregor! |
|
@swift-ci test |
| import XCTest | ||
| import SwiftDriver | ||
| import TSCBasic | ||
| import TSCUtility |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this import needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not right now, but we might need it to import Diagnostics.fatalError when we address the main.swift FIXME. For now I've dropped it.
… diagnostics from errors to warnings
5b73779 to
c21e733
Compare
|
@swift-ci test |
1 similar comment
|
@swift-ci test |
This PR adds validation for:
-profile-generateand-profile-use-Fand-FsystemAdditionally, if a validation step fails when initializing the driver, don't fail immediately. Instead, record any other validation failures and then exit before planning.