nicklockwood

import SwiftUI

enum OSDocumentError: Error {
    case unknownFileFormat
}

#if canImport(UIKit)

import UIKit

joscdk

.env files can be an easy way to setup Environment variables locally. You can start using a .env files in Vapor 3 by following this small guide.

First setup the vapor-ext package in your Package.swift file:

.package(url: "https://github.com/vapor-community/vapor-ext.git", from: "0.1.0"),

Next create a .env file in the root of your project:

vzsg

import Fluent

func fetchChildren<Parent, ParentID, Child: Model, Result>(
        of parents: [Parent],
        idKey: KeyPath<Parent, ParentID?>,
        via reference: KeyPath<Child, ParentID>,
        on conn: DatabaseConnectable,
        combining: @escaping (Parent, [Child]) -> Result) -> Future<[Result]> where ParentID: Hashable & Encodable {
    let parentIDs = parents.compactMap { $0[keyPath: idKey] }
    let children = Child.query(on: conn)

bjhomer

public extension NSLayoutConstraint.Priority {
    public static func -(lhs: NSLayoutConstraint.Priority, rhs: Float) -> NSLayoutConstraint.Priority {
        return NSLayoutConstraint.Priority(lhs.rawValue - rhs)
    }
    
    public static func +(lhs: NSLayoutConstraint.Priority, rhs: Float) -> NSLayoutConstraint.Priority {
        return NSLayoutConstraint.Priority(lhs.rawValue + rhs)
    }
}

jarsen

import Foundation

//
// MARK: - JSONError Type
//

public enum JSONError: ErrorType, CustomStringConvertible {
    case KeyNotFound(key: JSONKeyType)
    case NullValue(key: JSONKeyType)
    case TypeMismatch(expected: Any, actual: Any)

PurpleBooth

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

austinzheng

import Foundation

protocol SomeDelegateProtocol : class {
    func firstFunc() -> String
    func secondFunc() -> Bool
    func thirdFunc() -> Self
}

class MyClass {
    weak var delegate : SomeDelegateProtocol?

ordinaryzelig

I'm a fan of MiniTest::Spec. It strikes a nice balance between the simplicity of TestUnit and the readable syntax of RSpec. When I first switched from RSpec to MiniTest::Spec, one thing I was worried I would miss was the ability to add matchers. (A note in terminology: "matchers" in MiniTest::Spec refer to something completely different than "matchers" in RSpec. I won't get into it, but from now on, let's use the proper term: "expectations").

Understanding MiniTest::Expectations

Let's take a look in the code (I'm specifically referring to the gem, not the standard library that's built into Ruby 1.9):

# minitest/spec.rb

module MiniTest::Expectations

jcasimir

Render and Redirect

The normal controller/view flow is to display a view template corresponding to the current controller action, but sometimes we want to change that. We use render in a controller when we want to respond within the current request, and redirect_to when we want to spawn a new request.

Render

The render method is very overloaded in Rails. Most developers encounter it within the view template, using render :partial => 'form' or render @post.comments, but here we'll focus on usage within the controller.

:action

sstephenson

# Clone rbenv into ~/.rbenv
git clone git@github.com:sstephenson/rbenv.git ~/.rbenv

# Add rbenv to your PATH
# NOTE: rbenv is *NOT* compatible with rvm, so you'll need to 
# remove rvm from your profile if it's present. (This is because
# rvm overrides the `gem` command.)
echo 'export PATH="$HOME/.rbenv/bin:$HOME/.rbenv/shims:$PATH"' >> ~/.bash_profile
exec $SHELL