vabka

using System;
using System.IO;
using System.Threading.Tasks;
using PuppeteerSharp;

namespace pptrTest
{
    class Program
    {
        static async Task Main()

saschwarz

const API = Cypress.env('API');

const headers = {
    Authorization: '',
};

Cypress.Commands.add('loginUser', () => {
    return cy.readFile('aad-tokens.json')
        .then(creds => {
            // set auth headers so test setup calls are authorized

cdelgadob

const cleanTypenameLink = new ApolloLink((operation, forward) => {
      if (operation.variables) {
        operation.variables = this.omitDeep (operation.variables, "__typename")
      }
      return forward(operation).map((data) => {
        return data;
      })
    })

private omitDeep(obj, key) {

Billy-

Inspired by this issue on the lodash repo, asking for deep functionality for omit.

Note that there are plans to remove omit entirely in lodash v5... and props to this comment (and the one it quotes) in response to that 😆.

bvis

pipeline {
    agent { node { label 'swarm-ci' } }

    environment {
        TEST_PREFIX = "test-IMAGE"
        TEST_IMAGE = "${env.TEST_PREFIX}:${env.BUILD_NUMBER}"
        TEST_CONTAINER = "${env.TEST_PREFIX}-${env.BUILD_NUMBER}"
        REGISTRY_ADDRESS = "my.registry.address.com"

        SLACK_CHANNEL = "#deployment-notifications"

jacob-beltran

// How to ensure that our animation loop ends on component unount

componentDidMount() {
  this.startLoop();
}

componentWillUnmount() {
  this.stopLoop();
}

jbaxleyiii

import { Component } from "react";
import { print } from "graphql-tag/printer";
import { graphql } from "react-apollo";
import { MockedProvider } from "react-apollo/test-utils";
import { addTypenameToDocument } from "apollo-client/queries/queryTransform";

import { mount } from "enzyme";

import { withSavedPayments, SAVED_ACCTS_QUERY } from "../";

newyankeecodeshop

Background

Recently I noticed that Safari 10 for Mac/iOS had achieved 100% support for ES6. With that in mind, I began to look at the browser landscape and see how thorough the support in the other browsers. Also, how does that compare to Babel and its core-js runtime. According to an ES6 compatability table, Chrome, Firefox, and IE Edge have all surpassed what the Babel transpiler can generate in conjunction with runtime polyfills. The Babel/core-js combination achieves 71% support for ES6, which is quite a bit lower than the latest browsers provide.

It made me ask the question, "Do we need to run the babel es2015 preset anymore?", at least if our target audience is using Chrome, Firefox, or Safari.

It's clear that, for now, we can't create a site or application that only serves ES6. That will exclude users of Internet Explorer and various older browsers running on older iOS and Android devices. For example, Safari on iOS 9 has pretty mediocre ES6 support.

bastman

Docker - How to cleanup (unused) resources

Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...

delete volumes

// see: https://github.com/chadoe/docker-cleanup-volumes

$ docker volume rm $(docker volume ls -qf dangling=true)

$ docker volume ls -qf dangling=true | xargs -r docker volume rm

flipace

/**
 * Deep search and replaces the given property value "prevVal" with "newVal"
 * @param  {any} prevVal [description]
 * @param  {any} newVal  [description]
 * @param  {object|array} object the original object or array in which the values should be replaced
 * @return {object|array}        the new object or array
 */
function replacePropertyValue(prevVal, newVal, object) {
  const newObject = _.clone(object);