chrisidakwo

{
    "Abia": [
        "Aba North",
        "Aba South",
        "Arochukwu",
        "Bende",
        "Ikwuano",
        "Isiala-Ngwa North",
        "Isiala-Ngwa South",
        "Isuikwato",

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

chrisidakwo

#!/bin/sh
set -e
# Install node and npm via nvm - https://github.com/creationix/nvm

# Run this script like - bash script-name.sh

# Define versions
INSTALL_NODE_VER=10
INSTALL_NVM_VER=0.33.11
INSTALL_YARN_VER=1.7.0

chrisidakwo

/
# API Design Patterns And Use Cases


This document lists various useful patterns for API design. We encourage API developers to consider the following patterns as a guide while designing APIs for services.

### Document Semantics, Formatting, and Naming

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt).

chrisidakwo

Tinder API documentation

Note: this was written in April/May 2014 and the API may has definitely changed since. I have nothing to do with Tinder, nor its API, and I do not offer any support for anything you may build on top of this. Proceed with caution

http://rsty.org/

I've sniffed most of the Tinder API to see how it works. You can use this to create bots (etc) very trivially. Some example python bot code is here -> https://gist.github.com/rtt/5a2e0cfa638c938cca59 (horribly quick and dirty, you've been warned!)

chrisidakwo

Install Babel 7 and TypeScript

yarn add --dev \
  @babel/core \
  @babel/cli \
  @babel/preset-env \
  @babel/preset-typescript \
  typescript

chrisidakwo

Don't forget to set PHP Code Style to PSR-2 in your PHPStorm

---

1) Add Code Sniffer to composer.json file

composer require squizlabs/php_codesniffer

chrisidakwo

Connected Sum

A screenshot can be found here

Images

• https://media.cheggcdn.com/media/b9d/b9d19b2f-e7e9-43ed-80a8-f5cc4cbe8654/phplW5wFH.png
• https://media.cheggcdn.com/media/027/027c0228-323d-43ee-b9dd-a766b1548eb0/phpY2i471.png
• https://media.cheggcdn.com/media/f14/f1469362-2e60-44b8-9e91-db999d3002ed/phpvzNLiP.png

The question seems to have changed though

chrisidakwo

{
        "Abia": [
            "Aba",
            "Arochukwu",
            "Umuahia"
        ],
        "Adamawa": [
            "Jimeta",
            "Mubi",
            "Numan",

chrisidakwo

<?php

return [
    "Abia" => [
        "Aba North",
        "Aba South",
        "Arochukwu",
        "Bende",
        "Ikwuano",
        "Isiala-Ngwa North",