If your project uses third-party libraries or APIs, our general policy is to leave them "as is".
- Since Xcode offers great interoperability between Objective-C and Swift, you won't even care about the language used by your dependencies.
- Fixing conversion issues with the third-party code is generally trickier.
- Updating to a new version of the third-party framework would make you lose your changes.
- For most cases, there is an alternative third-party Swift library that you can switch to, rather than converting the Objective-C library to Swift.
In particular, our converter just skips contents of included libraries using CocoaPods or Carthage package managers.