Draft:SwiftLint
Submission declined on 28 June 2024 by SafariScribe (talk). This submission is not adequately supported by reliable sources. Reliable sources are required so that information can be verified. If you need help with referencing, please see Referencing for beginners and Citing sources. This draft's references do not show that the subject qualifies for a Wikipedia article. In summary, the draft needs multiple published sources that are:
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
|
Submission declined on 11 April 2024 by Hey man im josh (talk). This submission is not adequately supported by reliable sources. Reliable sources are required so that information can be verified. If you need help with referencing, please see Referencing for beginners and Citing sources. This draft's references do not show that the subject qualifies for a Wikipedia article. In summary, the draft needs multiple published sources that are: Declined by Hey man im josh 7 months ago.
|
Original author(s) | JP Simard |
---|---|
Initial release | May 30, 2015 |
Written in | Swift |
Operating system | macOS, Linux |
Available in | English |
Type | Static code analysis |
License | MIT |
Website | github |
SwiftLint,[1] is a static code analysis tool for the Swift programming language, that aims to enforce good Swift style and conventions. The creator and lead developer is JP Simard. It is the most commonly recommended Swift linter[2][3][4][5].
SwiftLint is free software under the MIT license.
Features
[edit]SwiftLint's checks are implemented as rules, which are either on by default, or opt-in.
Over 230 rules are built in to SwiftLint, and users can define additional custom rules using regular expressions.
For example, the identifier_name
[6] rule warns, or errors if identifiers (e.g. variable and function names) are too short or too long, and allows the warning and error thresholds for length, as well as identifiers that should be ignored by the rule (such as x
and y
), to be configured.
SwiftLint is also capable of auto-correcting certain kinds of violations.
SwiftLint has an analyzer mode, which can check for unused code and imports using the abstract syntax tree, but runs more slowly than the usual lint mode.
References
[edit]- ^ "SwiftLint". Website.
- ^ "SwiftLint in Depth - Kodeco". Website.
- ^ Vilmart, Florent; Scalzo, Gordiano; De Simone, Sergio (2018). Hands-On Design Patterns with Swift. Birmingham, UK: Pragmatic Bookshelf. ISBN 978-1789138511.
- ^ Nolan, Godfrey (2016). Agile Swift: Swift Programming Using Agile Tools and Techniques. Apress. ISBN 978-1484221020.
- ^ in 't Veen, Tjeerd (2018). Swift in Depth. Manning. ISBN 978-1638356165.
- ^ "identifier_name". Website.