GitPlanet

Cheap and reliable Node.js hosting starts at $3/month, and $1/month static HTML hosting

Created with love in Canada, visit hostnodejs.com today

Feel like to post an Ad? Learn Details
All Projects → malcommac → Swift-Coding-Guidelines

malcommac / Swift-Coding-Guidelines

Licence: other
A repository to collect best practices when programming with Swift

Labels

best-practiceslintercoding-styleswiftlint

Projects that are alternatives of or similar to Swift-Coding-Guidelines

mllint
`mllint` is a command-line utility to evaluate the technical quality of Python Machine Learning (ML) projects by means of static analysis of the project's repository.
Stars: ✭ 67 (+294.12%)
Mutual labels:  best-practices, linter
Go Consistent
Source code analyzer that helps you to make your Go programs more consistent.
Stars: ✭ 293 (+1623.53%)
Mutual labels:  best-practices, linter
Wotan
Pluggable TypeScript and JavaScript linter
Stars: ✭ 271 (+1494.12%)
Mutual labels:  best-practices, linter
Xo
❤️ JavaScript/TypeScript linter (ESLint wrapper) with great defaults
Stars: ✭ 6,277 (+36823.53%)
Mutual labels:  best-practices, linter
Pre Commit Hooks
A set of useful (and documented!) git pre-commit hooks.
Stars: ✭ 95 (+458.82%)
Mutual labels:  best-practices, linter
Validator
Nu Html Checker – Helps you catch problems in your HTML/CSS/SVG
Stars: ✭ 1,024 (+5923.53%)
Mutual labels:  best-practices, linter
Clusterlint
A best practices checker for Kubernetes clusters. 🤠
Stars: ✭ 409 (+2305.88%)
Mutual labels:  best-practices, linter
vscode-linter
Extension for code linting, all in one package. New linters can be easily added through an extension framework.
Stars: ✭ 47 (+176.47%)
Mutual labels:  linter, swiftlint
rubocop-graphql
Rubocop extension for enforcing graphql-ruby best practices
Stars: ✭ 143 (+741.18%)
Mutual labels:  best-practices, linter
vscode-protolint
A protobuf linter for visual studio code
Stars: ✭ 31 (+82.35%)
Mutual labels:  linter
standard-packages
List of packages that use `standard`
Stars: ✭ 32 (+88.24%)
Mutual labels:  linter
typeset.css
✍ tr.v. type·set To set (written material) into type; compose.
Stars: ✭ 19 (+11.76%)
Mutual labels:  best-practices
netflix-like-ios
Application to demonstrate how I develop an iOS App with VIPER architecture in 5 days (Swift only)
Stars: ✭ 30 (+76.47%)
Mutual labels:  swiftlint
architecture-guidelines
Project Architecture Guidelines Index
Stars: ✭ 14 (-17.65%)
Mutual labels:  best-practices
eslint-config
An ESLint shareable config that I used in my projects
Stars: ✭ 15 (-11.76%)
Mutual labels:  linter
eslint-plugin-ember-best-practices
Static analysis tools for enforcing best practices in Ember
Stars: ✭ 77 (+352.94%)
Mutual labels:  best-practices
stylelint-processor-glamorous
💄 Lint glamorous and related css-in-js with stylelint
Stars: ✭ 18 (+5.88%)
Mutual labels:  linter
automutate
Applies waves of mutations provided by other tools, such as linters or codemods.
Stars: ✭ 13 (-23.53%)
Mutual labels:  linter
cppbestpractices
Collaborative Collection of C++ Best Practices. This online resource is part of Jason Turner's collection of C++ Best Practices resources. See README.md for more information.
Stars: ✭ 5,424 (+31805.88%)
Mutual labels:  best-practices
elvis core
The core of an Erlang linter
Stars: ✭ 43 (+152.94%)
Mutual labels:  linter
View All Similar Projects ➔

Swift Coding Guidelines

The following section describe a list of rules, code conducts and best practices used while working on iOS projects using Swift language. With the help of a set of shared guidelines and automated tools we aim to maintain a higher level of code discipline and increase the reliability of the code during the entire lifecycle of a project.

The following section describe tools and rules used into the project. In order to automate the check of the source code by identifying some common and uncommon mistakes SwiftLint tool is used and executed at each build of the project.

Index

References

The following documents are used as base for this set of rules.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].