Open Source Swift Code Review Software

A tool to identify unused code in Swift projects. The scan command is Periphery's primary function. To begin a guided setup, simply change to your project directory. To get coherent results from Periphery, it's crucial to understand the implications of the build targets you choose to analyze. For example, imagine a project consisting of three targets: App, Lib and Tests. The App target imports Lib, and the Tests targets imports both App and Lib. If you were to provide all three to the --targets option then Periphery will be able to analyze your project as a whole. However, if you only choose to analyze App and Lib, but not Tests, Periphery may report some instances of unused code that are only referenced by Tests. Therefore when you suspect Periphery has provided an incorrect result, it's important to consider the targets that you have chosen to analyze.

Get strong typed, autocompleted resources like images, fonts and segues in Swift projects. It makes your code that uses resources to be fully typed, less casting and guessing what a method will return. Compile time checked, no more incorrect strings that make your app crash at runtime. Autocompleted, never have to guess that image name again. For autocompleted images, and compiletime checked images. After installing R.swift into your project you can use the R-struct to access resources. If the struct is outdated just build and R.swift will correct any missing/changed/added resources. Runtime validation with R.validate() ff all images used in storyboards and nibs are available, if all named colors used in storyboards and nibs are available, if all view controllers with storyboard identifiers can be loaded, if all custom fonts can be loaded.