chriseidhof

//
//  ParseLib.swift
//  JsxLib
//
//  Created by Chris Eidhof on 19.02.19.
//

import Foundation

public struct ParseError: Error {

vzsg

import Vapor
import SwiftProtobuf
import Foundation

extension Request {
    public func decodeMessage<M: SwiftProtobuf.Message>(_ type: M.Type = M.self) throws -> M {
        let data = http.body.data ?? Data()

        if http.contentType == MediaType.json {
            return try M(jsonUTF8Data: data)

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)

pedantix

import Foundation
import JWT
import Vapor

final class JWTService: Service {
  var signer: JWTSigner
  init(secret: String) {
    signer = JWTSigner.hs512(key: Data(secret.utf8))
  }

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

malarkey

When times get tough and people get nasty, you’ll need more than a killer smile. You’ll need a killer contract.

Used by 1000s of designers and developers Clarify what’s expected on both sides Helps build great relationships between you and your clients Plain and simple, no legal jargon Customisable to suit your business Used on countless web projects since 2008

…………………………