koingdev

lane :upload_testflight_on_pushing_tag do |options|
    # Tag: Release-1.0.0-100 (Release-Version-Build)
    tag_components = sh("git tag --sort=taggerdate | tail -1").split("-")
    version = tag_components[1]
    build = tag_components[2]
    
    # Increment version and build number
    increment_version_and_build_number(version: version, build: build)
    
    # Generate iPA

koingdev

Single-responsibility Principle

A class should have only one responsibility.

Bad

class ViewController: UIViewController {
	func fetchDataFromServer() { //Perform network request code... }
	func insertDataIntoDatabase() { //Perform database insertion code... }

koingdev

final class Brightness {
	
	// Config
	private let maxBrightness: CGFloat
	
	private(set) var defaultBrightness: CGFloat = 1.0
	
	var isEnabled = true {
		didSet {
			if isEnabled {

koingdev

/// Display ToolTip View
///
/// Example:
/// ```swift
///	let paragraph = NSMutableParagraphStyle()
///	paragraph.lineSpacing = 18
///	let attributes = [
///		NSAttributedString.Key.font : UIFont.systemFont(ofSize: 16),
///		NSAttributedString.Key.foregroundColor : UIColor.white,
///		NSAttributedString.Key.paragraphStyle : paragraph

koingdev

extension UIButton {
    func loadingIndicator(show: Bool, style: UIActivityIndicatorView.Style = .medium, color: UIColor = .white) {
        let tag = 10042017
        if show {
            isEnabled = false
            titleLabel?.alpha = 0
            let indicator = UIActivityIndicatorView(style: style)
            indicator.color = color
            indicator.center = CGPoint(x: bounds.size.width / 2, y: bounds.size.height / 2)
            indicator.tag = tag

koingdev

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

koingdev

1. Add new custom schema to schema.graphql file

2. Create custom request/response mapping resolvers file in resolvers folder. The file should look like this:

   • REQUEST_MAPPING: Mutation.putUser.req.vtl
   • RESPONSE_MAPPING: Mutation.putUser.res.vtl

3. Update CustomResources.json file in stack folder

koingdev

{
    "version" : "2017-02-28",
    "operation" : "PutItem",
    "key" : {
        "shopID": $util.dynamodb.toDynamoDBJson($ctx.args.shopID),
        "vendorID": $util.dynamodb.toDynamoDBJson($ctx.args.vendorID)
    },
    "attributeValues": {
        "name": $util.dynamodb.toDynamoDBJson($ctx.args.name)
    },

koingdev

{
    "version" : "2017-02-28",
    "operation" : "Query",
    "query" : {
        "expression" : "author = :author",
        "expressionValues" : {
        	":author" : $util.dynamodb.toDynamoDBJson($ctx.args.author)
        }
    },
    ## false -> DESC ORDER

koingdev

{
    "version" : "2017-02-28",
    "operation" : "PutItem",
    "key" : {
        "shopID" : $util.dynamodb.toDynamoDBJson($ctx.args.shopID),
        "id": $util.dynamodb.toDynamoDBJson($ctx.args.id)
    },
    "attributeValues" : {
        "staffName" : $util.dynamodb.toDynamoDBJson($ctx.args.staffName),
        "modifiedDate": $util.dynamodb.toDynamoDBJson($ctx.args.modifiedDate),