Warnings-xcconfig alternatives and similar libraries
Based on the "Code Quality" category.
Alternatively, view Warnings-xcconfig alternatives based on common mentions on social networks and blogs.
-
chisel
Chisel is a collection of LLDB commands to assist debugging iOS apps. -
MLeaksFinder
Find memory leaks in your iOS app at develop time. -
SwiftFormat
A command-line tool and Xcode Extension for formatting Swift code -
FBRetainCycleDetector
iOS library to help detecting retain cycles in runtime. -
FBMemoryProfiler
iOS tool that helps with profiling iOS Memory usage. -
CleanArchitectureRxSwift
Example of Clean Architecture of iOS app using RxSwift -
OCLint
A static source code analysis tool to improve quality and reduce defects for C, C++ and Objective-C -
KZBootstrap
iOS project bootstrap aimed at high quality coding. -
HeapInspector-for-iOS
Find memory issues & leaks in your iOS app without instruments -
Dotzu
iOS app debugger while using the app. Crash report, logs, network. -
dotenv-linter
⚡️Lightning-fast linter for .env files. Written in Rust 🦀 -
spacecommander
Commit fully-formatted Objective-C as a team without even trying. -
IBAnalyzer
Find common xib and storyboard-related problems without running your app or writing unit tests. -
ODUIThreadGuard
A guard to help you check if you make UI changes not in main thread -
DWURecyclingAlert
Optimizing UITableViewCell For Fast Scrolling -
SwiftCop
SwiftCop is a validation library fully written in Swift and inspired by the clarity of Ruby On Rails Active Record validations. -
GlueKit
Type-safe observable values and collections in Swift -
Marshroute
Marshroute is an iOS Library for making your Routers simple but extremely powerful -
PSTModernizer
Makes it easier to support older versions of iOS by fixing things and adding missing methods -
Trackable
Trackable is a simple analytics integration helper library. It’s especially designed for easy and comfortable integration with existing projects. -
DecouplingKit
decoupling between modules in your iOS Project. iOS模块化过程中模块间解耦方案 -
KZAsserts
Asserts on roids, test all your assumptions with ease. -
AnyLint
Lint anything by combining the power of scripts & regular expressions. -
WeakableSelf
A Swift micro-framework to easily deal with weak references to self inside closures -
UIBaseKit
This helps make the view's configuration code, hierarchy code, and constraint code neat. -
SwiftLinter
Share lint rules between projects and lint changed files with SwiftLint. -
Bugsee
In-app bug and crash reporting with video, logs, network traffic and traces.
Appwrite - The Open Source Firebase alternative introduces iOS support
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Warnings-xcconfig or a related project?
README
Warnings
This is an xcconfig file to make it easy for you to turn on a large suite of useful warnings in your Xcode project. These warnings catch bugs, so turning them on may identify bugs you can fix now and having them on will prevent bugs later.
If you have an existing project you've developed without these warnings turned on, you probably will have a number of warnings after turning them on. These are bugs in your code, newly revealed—fixing the warnings is fixing bugs.
The file also turns on Treat Warnings as Errors—so you can't just ignore warnings; you must fix them in order to be able to build—and the setting to run the Clang Static Analyzer in every build, which will find even more bugs (mostly leaks and crashers).
If you are new to Objective-C, you may find that you encounter build errors more frequently when using these settings. That is correct, expected, and good—the errors are bugs that would otherwise have gone undetected! Use these settings to identify your bad habits and things you don't fully understand, and take the opportunities to learn. You will learn better and faster with these warnings enabled.
The xcconfig file
Usage
- Copy it to your own project's root directory (the directory containing the .xcodeproj package).
- Add it to the project. In a modern project, it should be at the top level, either at the top of the list or below all of the per-target groups.
- Edit the project object (the very topmost item in the Project Navigator).
- Select the project, not any target.
- Select the Info tab.
- Under Configurations, expand both/all of the configurations.
- For each configuration, set the pop-up menu for the project to “Warnings” (which is the xcconfig file you just added).
What if you're already using an xcconfig file?
Xcode supports preprocessor directives in xcconfig files, so you can #include
the Warnings file from your existing xcconfig file.
The test project
WarningsTest is an Xcode project containing a unit test bundle target. The project uses the xcconfig file, and the tests demonstrate the kinds of bugs that the file tells the compiler to warn about.
Usage
Open it in Xcode, hold down on the verb button (the one that says Run by default) and choose Test. This will attempt to build the unit test bundle and run the tests.
It will fail, because the tests are all written to demonstrate the warnings, not to test other code. (There is no code under test.) Because of all the warnings and the Treat Warnings as Errors setting, the build will never succeed.
Credits
- Peter Hosey made a list of important warnings.
- Steven Fisher made the original xcconfig file of warning settings.