helfer

Migrating from Apollo Client 0.x to 1.0

Here are the main breaking changes between the 0.x and 1.0 versions of Apollo Client.

fetchMore

The structure of fetchMoreResult has been changed. Previously fetchMoreResult used to contain data and loading fields, now fetchMoreResult is what fetchMoreResult.data used to be. This means your updateQueries function has to change as follows:

updateQuery: (prev, { fetchMoreResult }) => {

nerdyworm

#!/bin/bash

set -e

CURRENT_NAME="CurentName"
CURRENT_OTP="current_name"

NEW_NAME="NewName"
NEW_OTP="new_name"

kylefox

A proposal for a framework-agnostic way of building Javascript configuration objects based on different environments.

This proposal focuses on the conventions that will allow for the creation of a plain old JavaScript object. For example:

var environment = new Environment("development");
environment.name; // "development"
environment.config.API_ROOT; // "http://localhost:3000/"

viniciussbs

List of HAFAS API Endpoints

This is a list of HAFAS API endpoints, all with different data versions, API versions, output formats and URL configurations. Help me complete this list!

todo: http://www.fahrplanauskunftssysteme.de/?seitenID=27

Deutsche Bahn (Germany)

• http://mobile.bahn.de/bin/extxml.exe or http://reiseauskunft.bahn.de/bin/extxml.exe
• http://mobile.bahn.de/bin/mobil/query.exe or http://mobile.bahn.de/bin/query.exe or http://reiseauskunft.bahn.de/bin/query.exe

brandur

Engineering API-driven Applications Using Service Stubs

Developing applications against foreign services like the Heroku Platform API can unlock a powerful set of otherwise unavailable features, but can come with drawbacks: development must occur online, valid credentials are required, calls your code makes will reveal and manipulate real data, and API calls in tests have to stubbed out individually.

This article will offer a short overview on how these pain points can be

brandur

Easy Twitter API OAuth 2 Access

1. Go to your applications. Create a new one, and find the values in the Consumer Key and Consumer Secret fields.

2. Use OAuth client information to produce an OAuth 2 access token:

   curl -i --user <consumer_key>:<consumer_secret> -X POST https://api.twitter.com/oauth2/token -d "grant_type=client_credentials"
   
   {"access_token":"<oauth2_token>","token_type":"bearer"}% 
   

vagnerzampieri

function mkcd(){
  mkdir $1;
  cd $1;
}
 
# Apt
alias apti='sudo apt-get install'
alias apts='sudo apt-cache search'
alias aptp='sudo apt-get --purge remove'
alias aptr='sudo apt-get remove'

viniciussbs

upstream tunnel {
  server 127.0.0.1:3000;
}

server {
  listen 80;
  server_name dev.codeplane.com br.dev.codeplane.com;
  
  location / {
    proxy_set_header  X-Real-IP  $remote_addr;

cgallagher

ActiveAdmin.register Milestone do
  scope :all, :default => true
  scope :global
  scope :user_specific
  
  index do
    column :title
    column :description
    column :required_litres
    column :is_active

tapajos

Migrando do Heroku para a Amazon Web Services

Recentemente eu comentei sobre a migração que fizemos no [Myfinance][mf] saindo do [Heroku][h] e indo para a [Amazon Web Services][a] e diversas pessoas me perguntaram as razões pela qual fizemos essa mudança. O objetivo desse post é apenas explicar a decisão que a nossa equipe tomou, como foi e as conseguências dessa migração.

Antes de começar eu gostaria de deixar claro que o objetivo desse texto não é comparar hospedagens e nem dizer que uma é melhor do que a outra. Trata-se apenas do relato de uma experiência.

A motivação

Antes de explicar a motivação por trás da migração é interessante mostrar como era a nossa estrutura.