-
Notifications
You must be signed in to change notification settings - Fork 1.2k
suggestedFilename always returns a valid filename #2643
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
Could you please add a test case for this? |
I'll need some time to see how test cases are done. |
They are just XCTest based tests in |
|
This comment has been minimized.
This comment has been minimized.
@Coeur I would recommend building on Windows or Linux. I suspect that you will need to adjust the Xcode build some since I imagine that the tests haven't been built with that for a while (normally the compatibility test suite is run on macOS). |
It should build fine on macOS in Xcode as that is how I develop on it. Use the default Xcode 11.3.1 toolchain and delete Ensure Ive just double-checked |
Oh, thank you @spevans, I forgot |
37229e8
to
6f551ae
Compare
@swift-ci test |
This comment has been minimized.
This comment has been minimized.
Sometimes the messages between github and swift-ci get lost, i'll start another test |
@swift-ci test |
@spevans @millenomi can we get it merged? Thank you. |
The Swift project moved the default branch to More detail about the branch update - https://forums.swift.org/t/updating-branch-names/40412 |
The property
suggestedFilename
is documented with:The default initializer
init(url:mimeType:expectedContentLength:textEncodingName:)
had a correct implementation, but the requiredinit?(coder:)
was unsafe.