Last 12 weeks · 0 commits
4 of 6 standards met
Can the dependency be renamed into something less abstract? I'm using an internal "Internal" static framework inside the project and it seems Xcode doesn't always like it. Every so often, especially when switching between build configurations and schemes, Xcode build would fail with an error. I'm guessing ExceptionCatcher sometimes confuses my internal framework with its own, and fails because of minimum deployment targets differences: Naming it into something less abstract might be a good thing in general, like ? Happy to make a PR of no one is against? P.S. Sorry for all the editing – hit the send button too early…
Repository: sindresorhus/ExceptionCatcher. Description: Catch Objective-C exceptions in Swift Stars: 179, Forks: 24. Primary language: Swift. Languages: Swift (75.1%), Objective-C (24.9%). License: MIT. Topics: exception-handler, exceptions, objective-c, swift-package. Latest release: v2.2.0 (1y ago). Open PRs: 0, open issues: 0. Last activity: 1y ago. Community health: 71%. Top contributors: sindresorhus, iby, tomlokhorst.