nickcernis

docker kill $(docker ps -q) to kill all running containers
docker rm $(docker ps -a -q) to delete all stopped containers.
docker volume rm $(docker volume ls -q) to delete all volumes.
docker rmi $(docker images -q) to delete all images.

Run all commands:

docker kill $(docker ps -q) && docker rm $(docker ps -a -q) && docker volume rm $(docker volume ls -q) && docker rmi $(docker images -q)

For fish shell, remove the $:

blak3r

'use strict';

module.exports = {
  up: (queryInterface, Sequelize) => {
    return queryInterface.addIndex('Parties', {
      fields: [Sequelize.literal('name gin_trgm_ops')],  // <-- name = field name, gin_trgm_ops comes after the field name
      using: 'gin',
      indexName: 'party_name_gin_trgm_idx', // specify the index name manually otherwise sequelize will create party_
      unique: false,
    })

rmarscher

// A script that can pull down the result of the introspection query
// from a running graphql server.

// Dependencies:
// npm i -S isomorphic-fetch graphql-tag graphql apollo-client

// Usage:
// node fetch-graphql-schema [graphql url]

// Example:

joshdover

Idiomatic React Testing Patterns

Testing React components seems simple at first. Then you need to test something that isn't a pure interaction and things seem to break down. These 4 patterns should help you write readable, flexible tests for the type of component you are testing.

Setup

I recommend doing all setup in the most functional way possible. If you can avoid it, don't set variables in a beforeEach. This will help ensure tests are isolated and make things a bit easier to reason about. I use a pattern that gives great defaults for each test example but allows every example to override props when needed:

craigbeck

  query IntrospectionQuery {
    __schema {
      queryType { name }
      mutationType { name }
      subscriptionType { name }
      types {
        ...FullType
      }
      directives {

mujimu

# start with es2016 skeleton
jspm install jquery
jspm install select2
jspm install css   # assure css handler in place for systemjs

Yimiprod

/**
 * This code is licensed under the terms of the MIT license
 *
 * Deep diff between two object, using lodash
 * @param  {Object} object Object compared
 * @param  {Object} base   Object to compare with
 * @return {Object}        Return a new object who represent the diff
 */
function difference(object, base) {
	function changes(object, base) {

alojzije

ancestral

/* 
 *  JavaScript Keyboard Map (Mac layout)
 *
 *
 *              esc—— F1——— F2——— F3——— F4——— F5——— F6——— F7——— F8——— F9——— F10—— F11—— F12—— F13—————+
 *             |  27 | 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 |  ???  |
 *            ` ——— 1———— 2———— 3———— 4———— 5———— 6———— 7———— 8———— 9———— 0———— - ——— = ——— delete——+
 *           | 192 |  49 |  50 |  51 |  52 |  53 |  54 |  55 |  56 |  57 |  58 |  59 |  60 |   61  |
 *          tab———— Q———— W———— E———— R———— T———— Y———— U———— I———— O———— P———— [ ——— ] ——— \ ————+
 *         |   9   |  81 |  87 |  69 |  82 |  84 |  89 |  85 |  73 |  79 |  80 | 219 | 221 | 220 |

stuarthalloway

;; Datomic sample code
;; schema query for attribute types in specified namespaces

(q '[:find ?attr
     :in $ [?include-ns ...]                ;; bind ?include-ns once for each item in collection
     :where
     [?e :db/valueType]                     ;; all schema types (must have a valueType)
     [?e :db/ident ?attr]                   ;; schema type name
     [(datomic.Util/namespace ?attr) ?ns]   ;; namespace of name
     [(= ?ns ?include-ns)]]                 ;; must match one of the ?include-ns