teamon

// === Basics
a must beMatching(bar)
a must be matching(bar)

a must not be matching(bar) // negation


// === Any object
a must_== b
a must_!= b

wfaler

// simple example of the cake pattern

// abstract DAO trait
trait Repository[A, B]{
  // saves an entity, returns an ID
  def save(entity: A): B
  // more features..
}

trait RdbmsRepository extends Repository[MyUserCaseClass, Long]{

vszakats

#!/bin/sh

# To the extent possible under law, Viktor Szakats
# has waived all copyright and related or neighboring rights to this
# script.
# CC0 - https://creativecommons.org/publicdomain/zero/1.0/
# SPDX-License-Identifier: CC0-1.0

# THIS SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

pantsel

version: "3"

networks:
 kong-net:
  driver: bridge

services:

  #######################################
  # Postgres: The database used by Kong

chrisidakwo

# API Design Guidelines


# Introduction

The PayPal platform is a collection of reusable services that encapsulate well-defined business capabilities. Developers are encouraged to access these capabilities through Application Programming Interfaces (APIs) that enable consistent design patterns and principles. This facilitates a great developer experience and the ability to quickly compose complex business processes by combining multiple, complementary capabilities as building blocks.

PayPal APIs follow the [RESTful][0] architectural style as much as possible. To support our objectives, we have developed a set of rules, standards, and conventions that apply to the design of RESTful APIs. These have been used to help design and maintain hundreds of APIs and have evolved over several years to meet the needs of a wide variety of use cases.

We are sharing these guidelines to help propagate good API design practices in general. We have pulled extensively from the broader community and believe that it is importan

naesean

JSONAPIObject:
  description: Includes the current JSON:API version for this specification as well as optional meta information
  type: object
  required:
    - version
  properties:
    version:
      type: string
      default: '1.0'
      example: '1.0'