swalkinshaw

Moved to Shopify/graphql-design-tutorial

danmakenoise

// Component.js
const Component = props => (
  <MyContext.Consumer>
    {(context) => (
      <Foo
        bar={props.bar}
        baz={context.baz}
      />
    )}
  </MyContext.Consumer>

varmais

<?php
function get_default_language_posts($query)
{
    if ($query->is_main_query() && is_home() && function_exists('pll_languages_list') && !is_admin()) {
        $languages = pll_languages_list(array('hide_empty' => 1));
        $terms = get_terms('post_translations');
        $lang_default = pll_default_language();
        $lang_current = pll_current_language();
        $post_ids = array();

maxvt

Currently, there is an explosion of tools that aim to manage secrets for automated, cloud native infrastructure management. Daniel Somerfield did some work classifying the various approaches, but (as far as I know) no one has made a recent effort to summarize the various tools.

This is an attempt to give a quick overview of what can be found out there. The list is alphabetical. There will be tools that are missing, and some of the facts might be wrong--I welcome your corrections. For the purpose, I can be reached via @maxvt on Twitter, or just leave me a comment here.

There is a companion feature matrix of various tools. Comments are welcome in the same manner.

jlong

var parser = document.createElement('a');
parser.href = "http://example.com:3000/pathname/?search=test#hash";

parser.protocol; // => "http:"
parser.hostname; // => "example.com"
parser.port;     // => "3000"
parser.pathname; // => "/pathname/"
parser.search;   // => "?search=test"
parser.hash;     // => "#hash"
parser.host;     // => "example.com:3000"

textarcana

#!/usr/bin/env bash

# Use this one-liner to produce a JSON literal from the Git log:

git log \
    --pretty=format:'{%n  "commit": "%H",%n  "author": "%aN <%aE>",%n  "date": "%ad",%n  "message": "%f"%n},' \
    $@ | \
    perl -pe 'BEGIN{print "["}; END{print "]\n"}' | \
    perl -pe 's/},]/}]/'

mtigas

Client-side SSL

For excessively paranoid client authentication.

---

Updated Apr 5 2019:

because this is a gist from 2011 that people stumble into and maybe you should AES instead of 3DES in the year of our lord 2019.

some other notes: