lisawolderiksen

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

phrozenra

import ApiBuilder from "claudia-api-builder";
import fetch from "node-fetch";
import FormData from "form-data";

let api = new ApiBuilder();

const verifyAndroidReceipt = req => {
  // setup credentials
  const config = {
    client_id: "<fill in>",

terrysahaidak

import { applySnapshot, onSnapshot } from 'mobx-state-tree';
import { transaction } from 'mobx';
import { AsyncStorage } from 'react-native';

const getSnapshots = (storesList, storage) => {
  const promises = storesList.map(storeName =>
    storage.getItem(storeName),
  );

  return Promise.all(promises).then(snapshots =>

paularmstrong

const plugins = [
  // extract vendor and webpack's module manifest
  new webpack.optimize.CommonsChunkPlugin({
    names: [ 'vendor', 'manifest' ],
    minChunks: Infinity
  }),
  // extract common modules from all the chunks (requires no 'name' property)
  new webpack.optimize.CommonsChunkPlugin({
    async: true,
    children: true,

sapessi

Continuous deployment of React websites to Amazon S3

This sample includes a continuous deployment pipiline for websites built with React. We use AWS CodePipeline, CodeBuild, and SAM to deploy the application. To deploy the application to S3 using SAM we use a custom CloudFormation resource.

Files included

• buildspec.yml: YAML configuration for CodeBuild, this file should be in the root of your code repository
• configure.js: Script executed in the build step to generate a config.json file for the application, this is used to include values exported by other CloudFormation stacks (separate services of the same application).
• index.js: Custom CloudFormation resource that publishes the website to an S3 bucket. As you can see from the buildspec and SAM template, this function is located in a s3-deployment-custom-resource sub-folder of the repo
• app-sam.yaml: Serverless Application model YAML file. This configures the S3 bucket and the cu

pablohpsilva

<template lang="html">
  <div @click="clicked()">oi</div>
</template>

<script type="text/babel">
  import ProductItem from '../../shared-components/Item';

  export default {
    extends: { // The Magic is happening right here
      props: {

davidgilbertson

@mixin for-size($size) {
  @if $size == phone-only {
    @media (max-width: 599px) { @content; }
  } @else if $size == tablet-portrait-up {
    @media (min-width: 600px) { @content; }
  } @else if $size == tablet-landscape-up {
    @media (min-width: 900px) { @content; }
  } @else if $size == desktop-up {
    @media (min-width: 1200px) { @content; }
  } @else if $size == big-desktop-up {

davidgilbertson

@mixin for-size($range) {
  $phone-upper-boundary: 600px;
  $tablet-portrait-upper-boundary: 900px;
  $tablet-landscape-upper-boundary: 1200px;
  $desktop-upper-boundary: 1800px;

  @if $range == phone-only {
    @media (max-width: #{$phone-upper-boundary - 1}) { @content; }
  } @else if $range == tablet-portrait-up {
    @media (min-width: $phone-upper-boundary) { @content; }

davidgilbertson

@mixin for-phone-only {
  @media (max-width: 599px) { @content; }
}
@mixin for-tablet-portrait-up {
  @media (min-width: 600px) { @content; }
}
@mixin for-tablet-landscape-up {
  @media (min-width: 900px) { @content; }
}
@mixin for-desktop-up {

chrisveness

/**
 * Generates a MongoDB-style ObjectId in Node.js. Uses nanosecond timestamp in place of counter; 
 * should be impossible for same process to generate multiple objectId in same nanosecond? (clock 
 * drift can result in an *extremely* remote possibility of id conflicts).
 *
 * @returns {string} Id in same format as MongoDB ObjectId.
 */
function objectId() {
    const os = require('os');
    const crypto = require('crypto');