Socially awkward act 1.7.1 – Inspect Xcode ventures for bugs and different issues.
Estimate: 22.56 MB
Socially awkward act reviews your iOS or Mac application’s Xcode extend and cautions about conceivable bugs, and about practicality and style issues.
What the Clang Static Analyzer is to your code, Faux Pas is to your entire Xcode extend. Blunder doesn’t simply take a gander at your code – it examines every one of the components of your Xcode extend together. This permits it to discover totally new classes of potential issues.
Tame dormant bugs – Rules like these ready you to issues in your venture that may show as bugs later down the line:
Discover asset record blunders – Are you certain you didn’t make a grammatical mistake in the filename contention to [UIImage imageNamed:]? Did you recollect to upgrade all pertinent code when you renamed that document? Is it true that you are transporting any asset records that are likely unused? Socially awkward act accompanies 12 distinct guidelines that check for blunders identified with asset record use.
Discover limitation blunders – Is NSLocalizedString() alluding to a key that does not exist? That exists for one district yet not another? Do the greater part of the organization specifiers in all the distinctive interpretations coordinate? Socially awkward act accompanies 10 unique decides that check for restriction blunders.
Discover variant control blunders – Is your venture referencing a record that is outside the rendition control root? Alternately a document that is disregarded by the VCS? Blunder accompanies 4 distinct guidelines that check for rendition control mistakes.
Learn and authorize best practices – Overriding +initializein a class? Indicating UIViewController NIB name outside of its usage? Getting to the address book without determining a NSContactsUsageDescription? Socially awkward act is valuable notwithstanding for experienced iOS/Mac designers, yet it’s particularly incredible for newcomers to Apple’s stages.
Authorize code style – Do you need to implement the utilization of speck punctuation at whatever point conceivable? On the other hand simply utilize it for properties proclaimed with @property? Shouldn’t something be said about NSNumber literals, boxed expressions, holder literals, and question subscripting? Blooper accompanies 12 unique decides that help you implement expressive limitations.
Get an agenda for code reviews – Are you examining or assuming control over a current codebase? Violation of social norms will give you a decent review of potential issues you might need to focus on.
Look over 93 changed standards – Faux Pas accompanies 93 rules, sorted utilizing labels like Resources, Style, or Config. You can pick which rules you need to apply, and arrange them to coordinate your inclinations.
Utilize GUI or CLI – Faux Pas has both a graphical UI and a charge line interface.
Keep running amid Xcode fabricates – Invoke Faux Pas in a Run Script manufacture stage in Xcode, and see the radiated diagnostics in Xcode’s Issue Navigator (and inline with the code, much the same as general compiler blunders).
Associate with outer apparatuses – Faux Pas can yield diagnostics in JSON or Property List designs. Prepare them in any capacity you need with custom scripts. You can likewise run Faux Pas on ceaseless mix servers.
Design – Select guidelines by labels, and reject singular standards. Set general and run particular choices. Spare into JSON setup records.
Open connections in your most loved supervisor Faux Pas can open records in a few famous code editors, and additionally API documentation in either Xcode or Dash.
Bolster for Xcode 8.1. (We now utilize a rendition of the Clang compiler that matches the one that boats with Xcode 8.1.)
New govern: Spelling blunder.
New administer: Source document header remark organize.
New manage: Erroneous view design in XIB.
New lead: Cyclomatic Complexity.
The “Missing API use portrayal” govern now checks for some more important cases.
Expelled the likelihood to open API documentation connects in (Xcode has expelled this ability from its AppleScript API since 8.0).
The “add explanations header record to venture” include now obliges you to physically add the header document to your Xcode extend (Xcode has evacuated the ability to add source documents to ventures from its AppleScript API since 8.0).
False positives for the “Constructor return sort” administer in situations where nullability explanations were utilized with instancetype. (On account of Nikolas Mayr for detailing this.)
Accumulation mistakes for undertakings utilizing C++14 highlights. (Because of Mark Hastings for detailing this.)
Hangs in the GUI when exchanging between Faux Pas and different applications. (Because of Andrew Wooster for announcing this.)
False negatives for the “Undetached delegate or information source” run in situations where the delegate have reference is an example variable proclaimed in a class expansion. (issue #100)
False positives for the “Dynamic library introduce name” run the show.
Unreasonable memory use in situations where checked source records contained vast quantities of indicative concealment full scale extensions. (Because of Nikolas Mayr for detailing this.)
Faux Pas for Mac
False positives for the “Hardcoded self class reference” control in situations where the reference is to a framework system class that is actualized as a class group (e.g. NSString). (On account of Nikolas Mayr for revealing this.)
False positives for the “Relegating delegate property” administer in situations where a similar header was utilized as a part of both ARC accumulation units and non-ARC assemblage units. (issue #99)
Hanging when opening ventures when utilizing Xcode 8.0-8.1. (issue #104)
OS X 10.9 or later, 64-bit processor