Consider validating that the SDK can be used from Swift 5 #57
Labels
testing
Includes all kinds of automated tests, the way that we run them and the infrastructure around them.
Comments
lawrence-forooghian
added
the
testing
lawrence-forooghian
added a commit
that referenced
this issue
Sep 18, 2024
We want to unlock Swift 6 features in the example app, the same way that 2cbf8dd did so for the SDK. It might be worth having some other small project that verifies that the SDK can be used by a project that targets Swift 5, but I don’t think this should be the example app, whose code should look modern and shiny. Created #57 to look into this sometime.
lawrence-forooghian
added a commit
that referenced
this issue
Sep 18, 2024
We want to unlock Swift 6 features in the example app, the same way that 67f4563 did so for the SDK. It might be worth having some other small project that verifies that the SDK can be used by a project that targets Swift 5, but I don’t think this should be the example app, whose code should look modern and shiny. Created #57 to look into this sometime.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider creating a Swift 5 project which gets built in CI, which validates that the project can be used from a Swift 5 project. (I think this is quite low priority, since I have a suspicion that all Swift 6 projects can be used from Swift 5, but if that's the case let's find something that documents that.)
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: