-
Notifications
You must be signed in to change notification settings - Fork 112
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
Test with Xcode 14.0 and Swift 5.7 #245
Conversation
`<blah ` | ||
""") | ||
if #available(iOS 16.0, tvOS 16.0, macOS 13.0, *) { | ||
XCTAssertEqual(ctx.debugDescription, column7) |
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.
Do we (want to) guarantee error output from Foundation? If so, this PR alone seems to indicate we cannot.
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 output seemed to be pretty stable up to this point, and I haven't found a different way to test the error context functionality end-to-end without being exposed to these caveats with how Foundation handle this.
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.
I'm happy to merge this with 5.7 test support, but we do need to evaluate the errors at some point.
Thanks, I've created #248 to track this. |
The way the XML parser from Foundation treats errors differs between SDK versions, we have to handle this in our tests accordingly.