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
Bump Swift version #4
Conversation
Also upgrade the Swift version to make Markdown module to be able to use DocC for documentation |
Any idea on this PR @QuietMisdreavus ❤️ |
0872f7e
to
bb40728
Compare
bb40728
to
27ff74c
Compare
Done, can we run tests on this PR? |
9504cbb
to
8fdd794
Compare
8fdd794
to
2853d7d
Compare
@swift-ci please test |
When I delete the
|
9cbd13d
to
2853d7d
Compare
It seems that Bundle.module is introduces on Swift 5.3 which is auto-generated for getting Package Resource.(You can check the file by recovering Package@swift-5.5.swift and Jump to Definition of // Autogenerated: resource_bundle_accessor.swift
import class Foundation.Bundle
private class BundleFinder {}
extension Foundation.Bundle {
/// Returns the resource bundle associated with the current Swift module.
static var module: Bundle = {
let bundleName = "swift-markdown_MarkdownTests"
let candidates = [
// Bundle should be present here when the package is linked into an App.
Bundle.main.resourceURL,
// Bundle should be present here when the package is linked into a framework.
Bundle(for: BundleFinder.self).resourceURL,
// For command-line tools.
Bundle.main.bundleURL,
]
for candidate in candidates {
let bundlePath = candidate?.appendingPathComponent(bundleName + ".bundle")
if let bundle = bundlePath.flatMap(Bundle.init(url:)) {
return bundle
}
}
fatalError("unable to find bundle named swift-markdown_MarkdownTests")
}()
} See https://developer.apple.com/documentation/swift_packages/bundling_resources_with_a_swift_package |
I think that's why people are not using the content of "Everything.md" to init the everythindDocument properly since the original swift version was 4.2 |
It seems we have 3 options to go, which one do you prefer? (Personally, I prefer option2, but option3 is also acceptable)
|
Fix "Package@swift-5.5.swift not pass the license check" issue
2853d7d
to
39516c1
Compare
cc @franklinsch |
Thanks for investigating these options! I think updating to 5.3 is reasonable (option 2) since it was released more than a year ago. |
Update to Swift 5.3 to support Bundle.module
Done. Could you please help me run test on this? |
@swift-ci please test this |
@swift-ci please test |
Any other suggestion on this? Or could we merge it with your approval? |
Looking at the CI logs, it looks like it's now emitting this warning:
Can we resolve this before merging this PR? |
Actually, I see that warning happened before the changes of this PR, so we can resolve this as part of another PR. |
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.
Thanks @Kyle-Ye for another awesome PR! 🙌
It seems to be fixed by this PR.(Which is blocked by this PR before) #3 |
This reverts commit 6d11986.
Summary
Bump the Swift version Package.swift use to 5.4. And add a new 5.5 Package.swift file
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.
./bin/test
script and it succeeded